Thread: log_error_verbosity placement

log_error_verbosity placement

From
Bruce Momjian
Date:
I just realized that log_error_verbosity is in the wrong section in
postgresql.conf and in our manual.  It is listed under "When to log"
when in fact it should be in the "What to log" section.

I also added documentation of what "terse" mode actually does.  I added
"verbosity" information a few weeks ago.

Patch attached.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +
Index: doc/src/sgml/config.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/config.sgml,v
retrieving revision 1.250
diff -c -c -r1.250 config.sgml
*** doc/src/sgml/config.sgml    5 Feb 2010 23:37:43 -0000    1.250
--- doc/src/sgml/config.sgml    9 Feb 2010 23:14:27 -0000
***************
*** 2833,2858 ****
        </listitem>
       </varlistentry>

-      <varlistentry id="guc-log-error-verbosity" xreflabel="log_error_verbosity">
-       <term><varname>log_error_verbosity</varname> (<type>enum</type>)</term>
-       <indexterm>
-        <primary><varname>log_error_verbosity</> configuration parameter</primary>
-       </indexterm>
-       <listitem>
-        <para>
-         Controls the amount of detail written in the server log for each
-         message that is logged.  Valid values are <literal>TERSE</>,
-         <literal>DEFAULT</>, and <literal>VERBOSE</>, each adding more
-         fields to displayed messages.  <literal>VERBOSE</> logging
-         output includes the <link
-         linkend="errcodes-appendix">SQLSTATE</> error
-         code and the source code file name, function name,
-         and line number that generated the error.
-         Only superusers can change this setting.
-        </para>
-       </listitem>
-      </varlistentry>
-
       <varlistentry id="guc-log-min-error-statement" xreflabel="log_min_error_statement">
        <term><varname>log_min_error_statement</varname> (<type>enum</type>)</term>
        <indexterm>
--- 2833,2838 ----
***************
*** 3172,3177 ****
--- 3152,3179 ----
        </listitem>
       </varlistentry>

+      <varlistentry id="guc-log-error-verbosity" xreflabel="log_error_verbosity">
+       <term><varname>log_error_verbosity</varname> (<type>enum</type>)</term>
+       <indexterm>
+        <primary><varname>log_error_verbosity</> configuration parameter</primary>
+       </indexterm>
+       <listitem>
+        <para>
+         Controls the amount of detail written in the server log for each
+         message that is logged.  Valid values are <literal>TERSE</>,
+         <literal>DEFAULT</>, and <literal>VERBOSE</>, each adding more
+         fields to displayed messages.  <literal>TERSE</> excludes
+         the logging of <literal>DETAIL</>, <literal>HINT</>,
+         <literal>QUERY</>, and <literal>CONTEXT</> error information.
+         <literal>VERBOSE</> output includes the <link
+         linkend="errcodes-appendix">SQLSTATE</> error
+         code and the source code file name, function name,
+         and line number that generated the error.
+         Only superusers can change this setting.
+        </para>
+       </listitem>
+      </varlistentry>
+
       <varlistentry id="guc-log-hostname" xreflabel="log_hostname">
        <term><varname>log_hostname</varname> (<type>boolean</type>)</term>
        <indexterm>
Index: src/backend/utils/misc/postgresql.conf.sample
===================================================================
RCS file: /cvsroot/pgsql/src/backend/utils/misc/postgresql.conf.sample,v
retrieving revision 1.276
diff -c -c -r1.276 postgresql.conf.sample
*** src/backend/utils/misc/postgresql.conf.sample    1 Feb 2010 13:40:28 -0000    1.276
--- src/backend/utils/misc/postgresql.conf.sample    9 Feb 2010 23:14:28 -0000
***************
*** 311,318 ****
                      #   fatal
                      #   panic

- #log_error_verbosity = default        # terse, default, or verbose messages
-
  #log_min_error_statement = error    # values in order of decreasing detail:
                       #   debug5
                      #   debug4
--- 311,316 ----
***************
*** 343,348 ****
--- 341,347 ----
  #log_connections = off
  #log_disconnections = off
  #log_duration = off
+ #log_error_verbosity = default        # terse, default, or verbose messages
  #log_hostname = off
  #log_line_prefix = ''            # special values:
                      #   %a = application name

Re: log_error_verbosity placement

From
Bruce Momjian
Date:
Applied.

---------------------------------------------------------------------------

Bruce Momjian wrote:
> I just realized that log_error_verbosity is in the wrong section in
> postgresql.conf and in our manual.  It is listed under "When to log"
> when in fact it should be in the "What to log" section.
> 
> I also added documentation of what "terse" mode actually does.  I added
> "verbosity" information a few weeks ago.
> 
> Patch attached.
> 
> -- 
>   Bruce Momjian  <bruce@momjian.us>        http://momjian.us
>   EnterpriseDB                             http://enterprisedb.com
> 
>   + If your life is a hard drive, Christ can be your backup. +


> 
> -- 
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +