comparison example_conf.toml @ 4624:209b10f7bb2c geoserver_sql_views

Add config for GeoServer database session startup SQL Prepended to setting the role in order to avoid any configuration overwriting it.
author Tom Gottfried <tom@intevation.de>
date Wed, 09 Oct 2019 18:47:13 +0200
parents 317d176ef38c
children 492fc5870330
comparison
equal deleted inserted replaced
4623:30bb2d819d57 4624:209b10f7bb2c
54 # Persisting this is mainly useful in some dev setups. 54 # Persisting this is mainly useful in some dev setups.
55 # Cleaning up the GeoServer should be done with 55 # Cleaning up the GeoServer should be done with
56 # an explicit --geoserver-clean on the command line. 56 # an explicit --geoserver-clean on the command line.
57 #geoserver-clean = true 57 #geoserver-clean = true
58 58
59 # geoserver-startup-sql can be used to add SQL commands to GeoServers database
60 # session start script. See
61 # https://docs.geoserver.org/stable/en/user/data/database/sqlsession.html
62 # Note that the commands will be executed as the user configured as 'db-user'.
63 # This can be used for example to set query planer configurations that fix
64 # bad query plans during GeoServer accessing the published layers.
65 # Currently, the published layer 'bottlenecks_geoserver' is known to trigger
66 # inefficient nested loop joins due to underestimation of the number of entries
67 # in the bottlenecks table. Hence the example setting:
68 geoserver-startup-sql = "SET enable_nestloop TO off"
69
59 # Proxy settings for external OGC services 70 # Proxy settings for external OGC services
60 #proxy-key = "SECRET" 71 #proxy-key = "SECRET"
61 #proxy-prefix = "http://localhost:8000" 72 #proxy-prefix = "http://localhost:8000"
62 # 73 #
63 74