aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2010-08-19 22:55:01 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2010-08-19 22:55:01 +0000
commit79dc97a401e8b51c3b91f3d629122b3f6c365a9f (patch)
treef8799d75c0ef71a9c458c7209e196113daf99e7a /doc/src
parent9676b01028139ca399f2564f6c4cb40fffe2ec07 (diff)
downloadpostgresql-79dc97a401e8b51c3b91f3d629122b3f6c365a9f.tar.gz
postgresql-79dc97a401e8b51c3b91f3d629122b3f6c365a9f.zip
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.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/config.sgml53
1 files changed, 26 insertions, 27 deletions
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 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.304 2010/08/17 04:37:20 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.305 2010/08/19 22:55:00 tgl Exp $ -->
<chapter Id="runtime-config">
<title>Server Configuration</title>
@@ -5777,6 +5777,31 @@ plruby.use_strict = true # generates error: unknown class name
</listitem>
</varlistentry>
+ <varlistentry id="guc-trace-recovery-messages" xreflabel="trace_recovery_messages">
+ <term><varname>trace_recovery_messages</varname> (<type>enum</type>)</term>
+ <indexterm>
+ <primary><varname>trace_recovery_messages</> configuration parameter</primary>
+ </indexterm>
+ <listitem>
+ <para>
+ Enables logging of recovery-related debugging output that otherwise
+ would not be logged. This parameter allows the user to override the
+ normal setting of <xref linkend="guc-log-min-messages">, but only for
+ specific messages. This is intended for use in debugging Hot Standby.
+ Valid values are <literal>DEBUG5</>, <literal>DEBUG4</>,
+ <literal>DEBUG3</>, <literal>DEBUG2</>, <literal>DEBUG1</>, and
+ <literal>LOG</>. The default, <literal>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 <literal>LOG</> priority; for common settings of
+ <varname>log_min_messages</> this results in unconditionally sending
+ them to the server log.
+ This parameter can only be set in the <filename>postgresql.conf</>
+ file or on the server command line.
+ </para>
+ </listitem>
+ </varlistentry>
+
<varlistentry id="guc-trace-sort" xreflabel="trace_sort">
<term><varname>trace_sort</varname> (<type>boolean</type>)</term>
<indexterm>
@@ -5959,32 +5984,6 @@ LOG: CleanUpLock: deleting: lock(0xb7acd844) id(24688,24696,0,0,0,1)
</listitem>
</varlistentry>
- <varlistentry id="guc-trace-recovery-messages" xreflabel="trace_recovery_messages">
- <term><varname>trace_recovery_messages</varname> (<type>enum</type>)</term>
- <indexterm>
- <primary><varname>trace_recovery_messages</> configuration parameter</primary>
- </indexterm>
- <listitem>
- <para>
- 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 <literal>DEBUG5</>, <literal>DEBUG4</>,
- <literal>DEBUG3</>, <literal>DEBUG2</>, <literal>DEBUG1</>,
- <literal>INFO</>, <literal>NOTICE</>, <literal>WARNING</>,
- <literal>ERROR</>, <literal>LOG</>, <literal>FATAL</>, and
- <literal>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 <literal>WARNING</>. Note that
- <literal>LOG</> has a different rank here than in
- <varname>client_min_messages</>.
- Parameter should be set in <filename>postgresql.conf</filename> only.
- </para>
- </listitem>
- </varlistentry>
-
<varlistentry id="guc-zero-damaged-pages" xreflabel="zero_damaged_pages">
<term><varname>zero_damaged_pages</varname> (<type>boolean</type>)</term>
<indexterm>