mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: document that INFO messages always go to client.

Browse Source 
In passing add a couple of links to the message severity table.

Backpatch because it's always been this way.

Author: Karl O. Pinc <kop@meme.com>
This commit is contained in:
Andrew Gierth 2019-01-07 18:19:46 +00:00
parent be2e329f2e
commit 93fedda6f0
1 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/src/sgml/config.sgml
View File

@ -5667,7 +5667,8 @@ local0.* /var/log/postgresql
</term> </term>
<listitem> <listitem>
<para> <para>
Controls which message levels are written to the server log. Controls which <link linkend="runtime-config-severity-levels">message
levels</link> are written to the server log.
Valid values are <literal>DEBUG5</literal>, <literal>DEBUG4</literal>, Valid values are <literal>DEBUG5</literal>, <literal>DEBUG4</literal>,
<literal>DEBUG3</literal>, <literal>DEBUG2</literal>, <literal>DEBUG1</literal>, <literal>DEBUG3</literal>, <literal>DEBUG2</literal>, <literal>DEBUG1</literal>,
<literal>INFO</literal>, <literal>NOTICE</literal>, <literal>WARNING</literal>, <literal>INFO</literal>, <literal>NOTICE</literal>, <literal>WARNING</literal>,
@ -5693,7 +5694,9 @@ local0.* /var/log/postgresql
Controls which SQL statements that cause an error Controls which SQL statements that cause an error
condition are recorded in the server log. The current condition are recorded in the server log. The current
SQL statement is included in the log entry for any message of SQL statement is included in the log entry for any message of
the specified severity or higher. the specified
<link linkend="runtime-config-severity-levels">severity</link>
or higher.
Valid values are <literal>DEBUG5</literal>, Valid values are <literal>DEBUG5</literal>,
<literal>DEBUG4</literal>, <literal>DEBUG3</literal>, <literal>DEBUG4</literal>, <literal>DEBUG3</literal>,
<literal>DEBUG2</literal>, <literal>DEBUG1</literal>, <literal>DEBUG2</literal>, <literal>DEBUG1</literal>,
@ -7025,7 +7028,9 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
</term> </term>
<listitem> <listitem>
<para> <para>
Controls which message levels are sent to the client. Controls which
<link linkend="runtime-config-severity-levels">message levels</link>
are sent to the client.
Valid values are <literal>DEBUG5</literal>, Valid values are <literal>DEBUG5</literal>,
<literal>DEBUG4</literal>, <literal>DEBUG3</literal>, <literal>DEBUG2</literal>, <literal>DEBUG4</literal>, <literal>DEBUG3</literal>, <literal>DEBUG2</literal>,
<literal>DEBUG1</literal>, <literal>LOG</literal>, <literal>NOTICE</literal>, <literal>DEBUG1</literal>, <literal>LOG</literal>, <literal>NOTICE</literal>,
@ -7035,6 +7040,9 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
<literal>NOTICE</literal>. Note that <literal>LOG</literal> has a different <literal>NOTICE</literal>. Note that <literal>LOG</literal> has a different
rank here than in <xref linkend="guc-log-min-messages"/>. rank here than in <xref linkend="guc-log-min-messages"/>.
</para> </para>
<para>
<literal>INFO</literal> level messages are always sent to the client.
</para>
</listitem> </listitem>
</varlistentry> </varlistentry>