More minor improvements to the SGML docs, namely

doc/src/sgml/runtime.sgml

Neil Conway

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 2ed1d06972a254ed7a50d0b5c3a82d0cfed831f4..6f659ab18ea07ba5f81ef6a62f420a35d41a612d 100644 (file)
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,5 +1,5 @@
 
 
 
@@ -1048,19 +1048,21 @@ env PGOPTIONS='-c geqo=off' psql
       LOG_MIN_ERROR_STATEMENT (string)
       
        
-        This controls for which message levels the SQL statement
-        causing that message is to be recorded in the server log. All
-        statements causing a message of the level of the setting or
-        higher are logged. The default is PANIC
-        (effectively turning this feature off). Valid values are
-        DEBUG5, DEBUG4,
-        DEBUG3, DEBUG2,
-        DEBUG1, INFO,
-        NOTICE, WARNING,
-        ERROR, FATAL, and
-        PANIC.  For example, if you set this to
-        ERROR then all SQL statements causing
-        errors, fatal errors, or panics will be logged.
+        Controls whether or not the SQL statement that causes an error
+        condition will also be recorded in the server log. All SQL
+        statements that cause an error of the specified level, or a
+        higher level, are logged.  The default is
+        PANIC (effectively turning this feature
+        off). Valid values are DEBUG5,
+        DEBUG4, DEBUG3,
+        DEBUG2, DEBUG1,
+        INFO, NOTICE,
+        WARNING, ERROR,
+        FATAL, and PANIC.  For
+        example, if you set this to ERROR then all
+        SQL statements causing errors, fatal errors, or panics will be
+        logged. Enabling this option can be helpful in tracking down
+        the source of any errors that appear in the server log.
        
 
        
@@ -1075,7 +1077,7 @@ env PGOPTIONS='-c geqo=off' psql
       LOG_MIN_MESSAGES (string)
       
        
-        This controls how much message detail is written to the server
+        Controls how much message detail is written to the server
         logs.  Valid values are DEBUG5,
         DEBUG4, DEBUG3, DEBUG2,
         DEBUG1, INFO, NOTICE,
@@ -1083,8 +1085,8 @@ env PGOPTIONS='-c geqo=off' psql
         FATAL, and PANIC. Later values send
         less detail to the logs.  The default is NOTICE.
         Note that LOG has a different precedence here than
-        in CLIENT_MIN_MESSAGES.  Also see that section 
-   for an explanation of the various values.
+        in CLIENT_MIN_MESSAGES.  Also see that section for
+        an explanation of the various values.
        
 
       
@@ -1155,11 +1157,12 @@ env PGOPTIONS='-c geqo=off' psql
       STATS_ROW_LEVEL (boolean)
       
        
-        These flags determine what information backends send to the statistics
-   collector process: current commands, block-level activity statistics,
-   or row-level activity statistics.  All default to off.  Enabling
-   statistics collection costs a small amount of time per query, but
-   is invaluable for debugging and performance tuning.
+        Determines what information backends send to the statistics
+        collector process: current commands, block-level activity
+        statistics, or row-level activity statistics.  All default to
+        off.  Enabling statistics collection costs a small amount of
+        time per query, but is invaluable for debugging and
+        performance tuning.
        
       
      
@@ -1180,10 +1183,11 @@ env PGOPTIONS='-c geqo=off' psql
       STATS_START_COLLECTOR (boolean)
       
        
-        Controls whether the server should start the statistics-collection
-   subprocess.  This is on by default, but may be turned off if you
-   know you have no interest in collecting statistics.  This option
-   can only be set at server start.
+        Controls whether the server should start the
+        statistics-collection subprocess.  This is on by default, but
+        may be turned off if you know you have no interest in
+        collecting statistics.  This option can only be set at server
+        start.
        
       
      
@@ -1209,7 +1213,7 @@ env PGOPTIONS='-c geqo=off' psql
        
         
           This option determines the syslog
-          facility to be used when
+          facility to be used when logging via
           syslog is enabled. You may choose
           from LOCAL0, LOCAL1,
           LOCAL2, LOCAL3, LOCAL4,
@@ -1689,23 +1693,23 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir'
      
 
      
-      MAX_FSM_RELATIONS (integer)
+      MAX_FSM_PAGES (integer)
       
        
-        Sets the maximum number of relations (tables) for which free
-        space will be tracked in the shared free-space map. The default
-        is 100. This option can only be set at server start.
+        Sets the maximum number of disk pages for which free space will
+        be tracked in the shared free-space map. The default is 10000.
+        This option can only be set at server start.
        
       
      
 
      
-      MAX_FSM_PAGES (integer)
+      MAX_FSM_RELATIONS (integer)
       
        
-        Sets the maximum number of disk pages for which free space will
-        be tracked in the shared free-space map. The default is 10000.
-        This option can only be set at server start.
+        Sets the maximum number of relations (tables) for which free
+        space will be tracked in the shared free-space map. The default
+        is 100. This option can only be set at server start.
        
       
      
@@ -1717,7 +1721,7 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir'
         The shared lock table is sized on the assumption that at most
         max_locks_per_transaction *
         max_connections distinct objects will need to
-        be locked at any one time. The default, 64, which has historically
+        be locked at any one time. The default, 64, has historically
         proven sufficient, but you might need to raise this value if you
         have clients that touch many different tables in a single
         transaction. This option can only be set at server start.