[Geoserver-users] Dropping columns in a database table for a production service [SEC=UNOFFICIAL]

GeoServer GeoServer User
1

Hi GeoServer user group!

I’m sure this question has been asked before, but on search I couldn’t find anything.

We have some production services running against a Postgres instance in which we’ve had to make some database modifications, namely dropping table columns that are no longer needed or were created in error.

Doing this to a production service causes the service to fail, as GeoServer seems to store the column names in memory. Doing a reboot of the service helps, but I was wondering whether there was a setting in GeoServer that allows a periodic refresh of the memory thus alleviating this problem? I’m sure there are performance considerations for changing this setting, but I’m happy to wear those for now.

We’re using GeoServer 2.14.x with a Tomcat JNDI resource for the Db connection.

Thanks

Michael

2

Go into the layer, find the Feature Type Details and the “refresh” button to update these details with the latest column names from your database.

These are stored as part of the GeoServer configuration and not cached in memory. You can also update these directly using REST API.

Docs: https://docs.geoserver.org/latest/en/user/data/webadmin/layers.html#feature-type-details-vector

···

–
Jody Garnett