Doc client_min_messages patch vis. INFO message severity
Hi,
Attached is documentation patch: doc_client_min_messages_v1.patch
Document that INFO severity messages are always sent
to the client. This also adds hyperlinks to the
table of severity levels where those levels are
referenced in the docs.
The patch was discussed on the #postgresql IRC channel
with RhodiumToad.
The patch is against master. It passes the xmllint,
builds html, and generally appears to work.
The motivation for this patch is that the
client_min_messages documentation does not mention
the INFO level.
Regards,
Karl <kop@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
Attachments:
doc_client_min_messages_v1.patchtext/x-patchDownload
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index e94b305add..a0098f93d1 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -5667,7 +5667,8 @@ local0.* /var/log/postgresql
</term>
<listitem>
<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>,
<literal>DEBUG3</literal>, <literal>DEBUG2</literal>, <literal>DEBUG1</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
condition are recorded in the server log. The current
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>,
<literal>DEBUG4</literal>, <literal>DEBUG3</literal>,
<literal>DEBUG2</literal>, <literal>DEBUG1</literal>,
@@ -7025,7 +7028,9 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
</term>
<listitem>
<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>,
<literal>DEBUG4</literal>, <literal>DEBUG3</literal>, <literal>DEBUG2</literal>,
<literal>DEBUG1</literal>, <literal>LOG</literal>, <literal>NOTICE</literal>,
@@ -7035,7 +7040,10 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
<literal>NOTICE</literal>. Note that <literal>LOG</literal> has a different
rank here than in <xref linkend="guc-log-min-messages"/>.
</para>
- </listitem>
+ <para>
+ <literal>INFO</literal> level messages are always sent to the client.
+ </para>
+ </listitem>
</varlistentry>
<varlistentry id="guc-search-path" xreflabel="search_path">
"Karl" == Karl O Pinc <kop@meme.com> writes:
Karl> Hi,
Karl> Attached is documentation patch: doc_client_min_messages_v1.patch
Karl> Document that INFO severity messages are always sent
Karl> to the client.
Pushed, thanks.
--
Andrew (irc:RhodiumToad)