Re: GUC and postgresql.conf docs - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: GUC and postgresql.conf docs
Date
Msg-id 200305121040.06064.josh@agliodbs.com
Whole thread Raw
In response to Re: GUC and postgresql.conf docs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: GUC and postgresql.conf docs  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom,

> The tables in src/backend/utils/misc/guc.c are the authoritative reference.
> Read the comments in src/include/utils/guc.h first.

Thanks.   Would never have found it on my own ...

> Yes, everything in postgresql.conf is a GUC variable; but I think there
> may be some GUC variables that were omitted from postgresql.conf.
> Hopefully intentionally, not by oversight ...

Mmm?   I think I have some terminology confusion somewhere.  I thought that a
GUC variable meant that it could be changed through a SET statement.  But
some settings, like TCP/IP socket, cannot be SET.   What distinguises
settings that can be SET from GUC variables that are restart-only?

I sense more posts to the list in the offing.

--
Josh Berkus
Aglio Database Solutions
San Francisco



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: GUC and postgresql.conf docs
Next
From: Tom Lane
Date:
Subject: Re: LIKE indexing proposal