From 79dc97a401e8b51c3b91f3d629122b3f6c365a9f Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Thu, 19 Aug 2010 22:55:01 +0000 Subject: 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. --- doc/src/sgml/config.sgml | 53 ++++++++++++++++++++++++------------------------ 1 file changed, 26 insertions(+), 27 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 5e0043ee7cb..d437727d335 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -1,4 +1,4 @@ - + Server Configuration @@ -5777,6 +5777,31 @@ plruby.use_strict = true # generates error: unknown class name + + trace_recovery_messages (enum) + + trace_recovery_messages configuration parameter + + + + Enables logging of recovery-related debugging output that otherwise + would not be logged. This parameter allows the user to override the + normal setting of , but only for + specific messages. This is intended for use in debugging Hot Standby. + Valid values are DEBUG5, DEBUG4, + DEBUG3, DEBUG2, DEBUG1, and + LOG. The default, LOG, does not affect + logging decisions at all. The other values cause recovery-related + debug messages of that priority or higher to be logged as though they + had LOG priority; for common settings of + log_min_messages this results in unconditionally sending + them to the server log. + This parameter can only be set in the postgresql.conf + file or on the server command line. + + + + trace_sort (boolean) @@ -5959,32 +5984,6 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1) - - trace_recovery_messages (enum) - - trace_recovery_messages configuration parameter - - - - Controls which message levels are written to the server log - for system modules needed for recovery processing. This allows - the user to override the normal setting of log_min_messages, - but only for specific messages. This is intended for use in - debugging Hot Standby. - Valid values are DEBUG5, DEBUG4, - DEBUG3, DEBUG2, DEBUG1, - INFO, NOTICE, WARNING, - ERROR, LOG, FATAL, and - PANIC. Each level includes all the levels that - follow it. The later the level, the fewer messages are sent - to the log. The default is WARNING. Note that - LOG has a different rank here than in - client_min_messages. - Parameter should be set in postgresql.conf only. - - - - zero_damaged_pages (boolean) -- cgit v1.2.3