You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Be more careful about GucSource for internally-driven GUC settings.
The original advice for hard-wired SetConfigOption calls was to usePGC_S_OVERRIDE, particularly for PGC_INTERNAL GUCs. However,that's really overkill for PGC_INTERNAL GUCs, since there is nopossibility that we need to override a user-provided setting.Instead use PGC_S_DYNAMIC_DEFAULT in most places, so that thevalue will appear with source = 'default' in pg_settings and therebynot be shown by psql's new \dconfig command. The one exception isthat when changing in_hot_standby in a hot-standby session, we stilluse PGC_S_OVERRIDE, because people felt that seeing that in \dconfigwould be a good thing.Similarly use PGC_S_DYNAMIC_DEFAULT for the auto-tune value ofwal_buffers (if possible, that is if wal_buffers wasn't explicitlyset to -1), and for the typical 2MB value of max_stack_depth.In combination these changes remove four not-very-interestingentries from the typical output of \dconfig, all of which peoplefingered as "why is that showing up?" in the discussion thread.Discussion:https://postgr.es/m/3118455.1649267333@sss.pgh.pa.us