Fix/compatability with latest postgres #81
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PostgreSQL version 17 breaks the plugin (see issue #71)
Version 17 introduced the following:
Change functions to use a safe search_path during maintenance operations (Jeff Davis) § §
This prevents maintenance operations (ANALYZE, CLUSTER, CREATE INDEX, CREATE MATERIALIZED VIEW, REFRESH MATERIALIZED VIEW, REINDEX, or VACUUM) from performing unsafe access. Functions used by expression indexes and materialized views that need to reference non-default schemas must specify a search path during function creation.
For us this meant that functions that are part of a
REFRESH MATERIALIZED VIEW
operation likest_snap_poly_to_grid
can no longer find PostGIS types (geometry) from the public schema because the path is temporarily changed to only include pg_catalog and pg_temp.As suggested the solution is to set the 'extra' schema in the function definition