Fix catalog staleness option#522
Merged
Merged
Conversation
This is a forward-port of PR duckdb#518. This is a follow-up PR to duckdb#514: - it changes the default scope of `pg_staleness_query_enabled` and `pg_staleness_query options` to `GLOBAL` to be easily usable from DuckLake (where `SESSION` options are not propagated to Postgres) - it changes the default value of `pg_staleness_query_enabled` to not run the staleness query by default in non-DuckLake scenarios
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is a forward-port of PR #518.
This is a follow-up PR to #514:
pg_staleness_query_enabledandpg_staleness_query optionstoGLOBALto be easily usable from DuckLake (whereSESSIONoptions are not propagated to Postgres)pg_staleness_query_enabledto not run the staleness query by default in non-DuckLake scenarios