Change true/false to on/off.

We prefer to use on/off than true/false for boolean configuration
parameters in the documentation, but there were a few places where
true/false were still used.

Dicussion: https://postgr.es/m/20181202.072508.618341295047874293.t-ishii%40sraoss.co.jp

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 2e5a5cd331ba059765de8f68eba2fef4fca7ece1..fc4f17be41b61f14ac8cca2b6e947ef76092213c 100644 (file)
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1249,7 +1249,7 @@ include_dir 'conf.d'
         than the client's.
         This parameter can only be set in the postgresql.conf
         file or on the server command line.
-        The default is true.
+        The default is on.
        
 
        
@@ -1404,12 +1404,12 @@ include_dir 'conf.d'
         This parameter determines whether the passphrase command set by
         ssl_passphrase_command will also be called during a
         configuration reload if a key file needs a passphrase.  If this
-        parameter is false (the default), then
+        parameter is off (the default), then
         ssl_passphrase_command will be ignored during a
         reload and the SSL configuration will not be reloaded if a passphrase
         is needed.  That setting is appropriate for a command that requires a
         TTY for prompting, which might not be available when the server is
-        running.  Setting this parameter to true might be appropriate if the
+        running.  Setting this parameter to on might be appropriate if the
         passphrase is obtained from a file, for example.
        
        
@@ -3330,14 +3330,14 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"'  # Windows
       
        
         Specifies whether to stop just after the specified recovery target
-        (true), or just before the recovery target
-        (false).
+        (on), or just before the recovery target
+        (off).
         Applies when ,
         , or
          is specified.
         This setting controls whether transactions
         having exactly the target WAL location (LSN), commit time, or transaction ID, respectively, will
-        be included in the recovery.  Default is true.
+        be included in the recovery.  Default is on.
        
       
      
@@ -8675,8 +8675,8 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
       
       
        
-        If true, any error will terminate the current session.  By default,
-        this is set to false, so that only FATAL errors will terminate the
+        If on, any error will terminate the current session.  By default,
+        this is set to off, so that only FATAL errors will terminate the
         session.
        
       
@@ -8690,9 +8690,9 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
       
       
        
-        When set to true, which is the default, PostgreSQL
+        When set to on, which is the default, PostgreSQL
         will automatically reinitialize after a backend crash.  Leaving this
-        value set to true is normally the best way to maximize the availability
+        value set to on is normally the best way to maximize the availability
         of the database.  However, in some circumstances, such as when
         PostgreSQL is being invoked by clusterware, it may be
         useful to disable the restart so that the clusterware can gain
@@ -8709,7 +8709,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
       
       
        
-        When set to false, which is the default, PostgreSQL
+        When set to off, which is the default, PostgreSQL
         will raise a PANIC-level error on failure to flush modified data files
         to the filesystem.  This causes the database server to crash.
        
@@ -8724,9 +8724,9 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
         faulty hardware.
        
        
-        If set to true, PostgreSQL will instead
+        If set to on, PostgreSQL will instead
         report an error but continue to run so that the data flushing
-        operation can be retried in a later checkpoint.  Only set it to true
+        operation can be retried in a later checkpoint.  Only set it to on
         after investigating the operating system's treatment of buffered data
         in case of write-back failure.