Fix enable_job_execution_logging
GUC context
#7131
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.
In #6767 we allowed users to track job execution history by turning on the new GUC
timescaledb.enable_job_execution_logging
.Unfortunately we defined this GUC as PGC_USERSET context but the right context should be PGC_SIGHUP since it won't work when setting at session and/or database level so we should restrict it to be used only by
ALTER SYSTEM SET
or changing the config files.Disable-check: force-changelog-file