Re: Incorrect GUC descriptions in docs and postgresql.conf.sample - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: Incorrect GUC descriptions in docs and postgresql.conf.sample
Date
Msg-id 20210526014314.GH3676@telsasoft.com
Whole thread Raw
In response to Incorrect GUC descriptions in docs and postgresql.conf.sample  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Incorrect GUC descriptions in docs and postgresql.conf.sample
List pgsql-hackers
Your patch adds documentation about GUCs that can only be set at server
start/config/commandline.

But it's not true for any of these, which are all HUP/SUSET.
Please double check your logic :)

src/backend/utils/misc/guc.c:           {"autovacuum_work_mem", PGC_SIGHUP, RESOURCES_MEM,
src/backend/utils/misc/guc.c:           {"remove_temp_files_after_crash", PGC_SIGHUP, ERROR_HANDLING_OPTIONS,
src/backend/utils/misc/guc.c:           {"restart_after_crash", PGC_SIGHUP, ERROR_HANDLING_OPTIONS,
src/backend/utils/misc/guc.c:           {"log_lock_waits", PGC_SUSET, LOGGING_WHAT,
src/backend/utils/misc/guc.c:           {"autovacuum_work_mem", PGC_SIGHUP, RESOURCES_MEM,
src/backend/utils/misc/guc.c:           {"ssl_max_protocol_version", PGC_SIGHUP, CONN_AUTH_SSL,
src/backend/utils/misc/guc.c:           {"ssl_min_protocol_version", PGC_SIGHUP, CONN_AUTH_SSL,

-- 
Justin



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: storing an explicit nonce
Next
From: Bruce Momjian
Date:
Subject: Re: storing an explicit nonce