doc: document that INFO messages always go to client.

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

Backpatch because it's always been this way.

Author: Karl O. Pinc 

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 79bd64dccd54c7c15e15eb1cb1b912e0fef36630..8999eee5f14ca795b081503c02da9a5d8fcaa2e1 100644 (file)
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -5085,7 +5085,8 @@ local0.*    /var/log/postgresql
       
       
        
-        Controls which message levels are written to the server log.
+        Controls which message
+        levels are written to the server log.
         Valid values are DEBUG5, DEBUG4,
         DEBUG3, DEBUG2, DEBUG1,
         INFO, NOTICE, WARNING,
@@ -5111,7 +5112,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
+        severity
+        or higher.
         Valid values are DEBUG5,
         DEBUG4, DEBUG3,
         DEBUG2, DEBUG1,
@@ -6423,7 +6426,9 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
       
       
        
-        Controls which message levels are sent to the client.
+        Controls which
+        message levels
+        are sent to the client.
         Valid values are DEBUG5,
         DEBUG4, DEBUG3, DEBUG2,
         DEBUG1, LOG, NOTICE,
@@ -6433,6 +6438,9 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
         NOTICE.  Note that LOG has a different
         rank here than in .
        
+       
+        INFO level messages are always sent to the client.
+