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.
config.sgml (r1.304 -> r1.305)
standby.c (r1.28 -> r1.29)
elog.c (r1.225 -> r1.226)
guc.c (r1.567 -> r1.568)
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2010-08-19 22:55:10|
|Subject: pgsql: Bring some sanity to the trace_recovery_messages code and docs.|
|Previous:||From: Tom Lane||Date: 2010-08-19 18:58:11|
|Subject: pgsql: Allow USING and INTO clauses of plpgsql's EXECUTE to appear in |