Bring some sanity to the trace_recovery_messages code and docs.

Tom Lane <tgl@sss.pgh.pa.us>

Commit: f333f69d1919399e07a08d06f4bb7ffc5fae49b6
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: 2010-08-19T22:55:10Z
Releases: 9.0.0
Bring some sanity to the trace_recovery_messages code and docs.
Per gripe from Fujii Masao, though this is not exactly his proposed patch.
Categorize as DEVELOPER_OPTIONS and set context PGC_SIGHUP, as per Fujii,
but set the default to LOG because higher values aren't really sensible
(see the code for trace_recovery()).  Fix the documentation to agree with
the code and to try to explain what the variable actually does.  Get rid
of no-op calls trace_recovery(LOG), which accomplish nothing except to
demonstrate that this option confuses even its author.

Files

PathChange+/−
doc/src/sgml/config.sgml modified +26 −27
src/backend/storage/ipc/standby.c modified +3 −3
src/backend/utils/error/elog.c modified +11 −4
src/backend/utils/misc/guc.c modified +8 −4