Re: GUC and postgresql.conf docs

Tom, Peter,

Since I had to do this anyway, I thought the following would help you clean up
a little.  Please check my report for accuracy; postgresql.conf.sample lists
the GUC variables in one order, the online documentation in another, and
guc.c in a third, completely different order.  So it's entirely possible I
missed something.

BTW, my next proposal after finishing this list will be to re-order the
variables in postgresql.conf.sample into something more logical than the
current "incremental development order".  Expect it next week.

GUC Options with no documentation:
The following options exist in postgresql.conf.sample and in guc.c but not in
the online documenation anywhere the search box can find:

trace_locks
trace_userlocks
trace_lwlocks
debug_deadlocks
trace_lock_oidmin
trace_lock_table

show_btree_build_stats


Defined in guc.c but not in PostgreSQL.conf or docs:
The following four GUC variables are defined in guc.c, but are not included in
postgresql.conf.sample, and do not show up in the online docs under anything
I can search on.  Do they do anything?  If so, what?


{"fixbtree", PGC_POSTMASTER}, &FixBTree,    true, NULL, NULL
{"pre_auth_delay", PGC_SIGHUP}, &PreAuthDelay,    0, 0, 60, NULL, NULL
{"server_encoding", PGC_USERSET}, &server_encoding_string,    "SQL_ASCII", assign_server_encoding, show_server_encoding
{"session_authorization", PGC_USERSET, GUC_NO_SHOW_ALL | GUC_NO_RESET_ALL},    &session_authorization_string,    NULL,
assign_session_authorization,show_session_authorization     

Defined in guc.c and docs but not in postgresql.conf:
These four related settings are defined guc's that somehow made it into the
docs but not into postgresql.conf.sample:

{"lc_messages", PGC_SUSET}, &locale_messages,
"", locale_messages_assign, NULL

{"lc_monetary", PGC_USERSET}, &locale_monetary,
"C", locale_monetary_assign, NULL

{"lc_numeric", PGC_USERSET}, &locale_numeric,
"C", locale_numeric_assign, NULL

{"lc_time", PGC_USERSET}, &locale_time,
"C", locale_time_assign, NULL


Hope that helps clean up for the next release!

--
Josh Berkus
Aglio Database Solutions
San Francisco