Thread: GUC/postgresql.conf docs

is it posted anywhere which GUC variables are reset upon pg_ctl reload
and which require a pg_ctl restart to take effect?

thanks.

-tfo

"Thomas O'Connell" <tfo@monsterlabs.com> writes:
> is it posted anywhere which GUC variables are reset upon pg_ctl reload
> and which require a pg_ctl restart to take effect?

The ones for which the Admin Guide says "this can only be set at server
start" are in the latter class.

            regards, tom lane

I just wanted to make sure the list was exhaustive. What of those that
are marked "startup or postgresql.conf"? Do those respond to pg_ctl
reload if modified in postgresql.conf while postmaster is running?

Thanks!

-tfo

On Monday, January 13, 2003, at 02:05 , Tom Lane wrote:

> "Thomas O'Connell" <tfo@monsterlabs.com> writes:
>> is it posted anywhere which GUC variables are reset upon pg_ctl reload
>> and which require a pg_ctl restart to take effect?
>
> The ones for which the Admin Guide says "this can only be set at server
> start" are in the latter class.
>
>             regards, tom lane

"Thomas F.O'Connell" <tfo@monsterlabs.com> writes:
> I just wanted to make sure the list was exhaustive. What of those that
> are marked "startup or postgresql.conf"?

I believe the latter are the ones you cannot set per-backend.

If you want to be certain, look through src/backend/utils/misc/guc.c
to see which variables are marked PGC_POSTMASTER.  Those are the
restart-required vars.  The ones marked PGC_SIGHUP can be changed from
postgresql.conf, but not per-backend.  (See comments in
src/include/utils/guc.h for the gory details.)

If you find any for which the Admin Guide is wrong or misleading,
please submit a docs patch ...

            regards, tom lane