Order some new options on man pages more sensibly, minor improvements

diff --git a/doc/src/sgml/ref/alter_database.sgml b/doc/src/sgml/ref/alter_database.sgml
index 787cfff16736e04cd01d0dd912baf30ae65c5238..cfc28cf9a7708b9a278117b02cd73f223b2ef6f0 100644 (file)
--- a/doc/src/sgml/ref/alter_database.sgml
+++ b/doc/src/sgml/ref/alter_database.sgml
@@ -25,9 +25,9 @@ ALTER DATABASE name [ [ WITH ] 
 
 where option can be:
 
-    IS_TEMPLATE istemplate
     ALLOW_CONNECTIONS allowconn
     CONNECTION LIMIT connlimit
+    IS_TEMPLATE istemplate
 
 ALTER DATABASE name RENAME TO new_name
 
@@ -110,17 +110,6 @@ ALTER DATABASE name RESET ALL
       
      
 
-     
-       istemplate
-       
-        
-         If true, then this database can be cloned by any user with CREATEDB
-         privileges; if false, then only superusers or the owner of the
-         database can clone it.
-        
-       
-      
-
       
        allowconn
        
@@ -140,6 +129,17 @@ ALTER DATABASE name RESET ALL
       
      
 
+     
+       istemplate
+       
+        
+         If true, then this database can be cloned by any user with CREATEDB
+         privileges; if false, then only superusers or the owner of the
+         database can clone it.
+        
+       
+      
+
    
     new_name
     

diff --git a/doc/src/sgml/ref/create_database.sgml b/doc/src/sgml/ref/create_database.sgml
index 0d187e29f523690ccc6c5a9ce9a48e1153657a65..138996bedc804382177585c12c0eb88b1da1fc03 100644 (file)
--- a/doc/src/sgml/ref/create_database.sgml
+++ b/doc/src/sgml/ref/create_database.sgml
@@ -28,9 +28,9 @@ CREATE DATABASE name
            [ LC_COLLATE [=] lc_collate ]
            [ LC_CTYPE [=] lc_ctype ]
            [ TABLESPACE [=] tablespace_name ]
-           [ IS_TEMPLATE [=] istemplate ]
            [ ALLOW_CONNECTIONS [=] allowconn ]
            [ CONNECTION LIMIT [=] connlimit ] ]
+           [ IS_TEMPLATE [=] istemplate ]
 
  
 
@@ -149,17 +149,6 @@ CREATE DATABASE name
       
      
 
-     
-       istemplate
-       
-        
-         If true, then this database can be cloned by any user with CREATEDB
-         privileges; if false (the default), then only superusers or the owner
-         of the database can clone it.
-        
-       
-      
-
       
        allowconn
        
@@ -180,6 +169,17 @@ CREATE DATABASE name
        
       
      
+
+      
+       istemplate
+       
+        
+         If true, then this database can be cloned by any user with CREATEDB
+         privileges; if false (the default), then only superusers or the owner
+         of the database can clone it.
+        
+       
+      
     
 
   

diff --git a/doc/src/sgml/ref/create_policy.sgml b/doc/src/sgml/ref/create_policy.sgml
index 629ed801f24d4043484b8ec2e449f1fb12591441..7b4f9438cd517c70260ba4350431b90607b8fefd 100644 (file)
--- a/doc/src/sgml/ref/create_policy.sgml
+++ b/doc/src/sgml/ref/create_policy.sgml
@@ -34,7 +34,7 @@ CREATE POLICY name ON 
 
   
    The CREATE POLICY command defines a new policy for a
-   table.  Note that row level security must also be enabled on the table using
+   table.  Note that row-level security must also be enabled on the table using
    ALTER TABLE in order for created policies to be applied.
   
 

diff --git a/doc/src/sgml/ref/pg_ctl-ref.sgml b/doc/src/sgml/ref/pg_ctl-ref.sgml
index 2df65db0bdde136199122480829d02ff3eb490fe..eaa0cc8b3701e09038a1f69063216026976d7d60 100644 (file)
--- a/doc/src/sgml/ref/pg_ctl-ref.sgml
+++ b/doc/src/sgml/ref/pg_ctl-ref.sgml
@@ -427,10 +427,10 @@ PostgreSQL documentation
        Name of the event source for pg_ctl to use
        for logging to the event log when running as a Windows service.  The
        default is PostgreSQL.  Note that this only controls
-       the logging from pg_ctl itself - once
+       the logging from pg_ctl itself; once
        started, the server will use the event source specified
        by .  Should the server fail during
-       early startup, it may also log using the default event
+       early startup, it might also log using the default event
        source PostgreSQL.
       
      

diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index cfaec967403c3211df44af51b3aa505cc806156a..9d84f8b4cc3e719c3f4cc0780b9cb7953887510a 100644 (file)
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -707,13 +707,13 @@ PostgreSQL documentation
       
        
         This option is relevant only when dumping the contents of a table
-        which has row security.  By default, pg_dump will set
-        <literal>ROW_SECURITY to OFF, to ensure
+        which has row security.  By default, pg_dump will set
+        <xref linkend="guc-row-security"> to off, to ensure
         that all data is dumped from the table.  If the user does not have
         sufficient privileges to bypass row security, then an error is thrown.
         This parameter instructs pg_dump to set
-        row_security to 'ON' instead, allowing the user to dump the contents
-        of the table which they have access to.
+         to on instead, allowing the user
+        to dump the parts of the contents of the table that they have access to.
        
 
       
@@ -862,27 +862,6 @@ PostgreSQL documentation
        
      
 
-     
-       --snapshot=snapshotname
-       
-         
-          Use the specified synchronized snapshot when making a dump of the
-          database (see
-           for more
-          details).
-         
-         
-          This option is useful when needing to synchronize the dump with
-          a logical replication slot (see )
-          or with a concurrent session.
-         
-         
-          In the case of a parallel dump, the snapshot name defined by this
-          option is used rather than taking a new snapshot.
-         
-       
-     
-
      
       --serializable-deferrable
       
@@ -918,6 +897,27 @@ PostgreSQL documentation
       
      
 
+     
+       --snapshot=snapshotname
+       
+         
+          Use the specified synchronized snapshot when making a dump of the
+          database (see
+           for more
+          details).
+         
+         
+          This option is useful when needing to synchronize the dump with
+          a logical replication slot (see )
+          or with a concurrent session.
+         
+         
+          In the case of a parallel dump, the snapshot name defined by this
+          option is used rather than taking a new snapshot.
+         
+       
+     
+
      
       --use-set-session-authorization
       

diff --git a/doc/src/sgml/ref/pg_receivexlog.sgml b/doc/src/sgml/ref/pg_receivexlog.sgml
index 0e6ec1c414467064bc5bf68560a7a882186002ab..0dcba4d54fb7f1ce44609938343af996435a1f13 100644 (file)
--- a/doc/src/sgml/ref/pg_receivexlog.sgml
+++ b/doc/src/sgml/ref/pg_receivexlog.sgml
@@ -50,7 +50,7 @@ PostgreSQL documentation
 
   
    Unlike the standby's WAL receiver, pg_receivexlog
-   flushes WAL data only when a WAL file is closed, by default.
+   by default flushes WAL data only when a WAL file is closed.
    --synchronous option must be specified to flush WAL data
    in real time and ensure it's safely flushed to disk.
   

diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml
index a5a939443d90ce0b7aa51c0b1ea74b4dffe80d39..66d09f4209046537585aac88d13a8d70611a37d7 100644 (file)
--- a/doc/src/sgml/ref/pg_restore.sgml
+++ b/doc/src/sgml/ref/pg_restore.sgml
@@ -520,25 +520,25 @@
      
 
      
-      --enable-row-security                                                          
+      --enable-row-security
+      
        
         This option is relevant only when restoring the contents of a table
-        which has row security.  By default, pg_restore will set
-        <literal>ROW_SECURITY to OFF, to ensure
+        which has row security.  By default, pg_restore will set
+        <xref linkend="guc-row-security"> to off, to ensure
         that all data is restored in to the table.  If the user does not have
         sufficient privileges to bypass row security, then an error is thrown.
         This parameter instructs pg_restore to set
-        row_security to 'ON' instead, allowing the user to attempt to restore
-        the contents of the table with row security enabled.  This may still
+         to on instead, allowing the user to attempt to restore
+        the contents of the table with row security enabled.  This might still
         fail if the user does not have the right to insert the rows from the
         dump into the table.
        
 
        
-        Note that this option currently also requires the dump be in INSERT
-        format as COPY TO does not support row security.
+        Note that this option currently also requires the dump be in INSERT
+        format, as COPY TO does not support row security.
        
-
       
      
 

diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml
index 43c05d570cec8802cbac9915bfc1b24c4f3010f0..9cdfa902f5acfcdeb2442a4f21e7acc404974564 100644 (file)
--- a/doc/src/sgml/ref/pg_rewind.sgml
+++ b/doc/src/sgml/ref/pg_rewind.sgml
@@ -81,6 +81,16 @@ PostgreSQL documentation
    recovery.conf file in the target data directory with a
    suitable restore_command.
   
+
+  
+   pg_rewind requires that the target server either has
+   the  option is enabled
+   in postgresql.conf or that data checksums were enabled when
+   the cluster was initialized with initdb.  Neither of these
+   are currently on by default.
+    must also be enabled.  That is the
+   default.
+  
  
 
  
@@ -159,13 +169,13 @@ PostgreSQL documentation
      
       -V
       --version
-      Display version information, then exit
+      Display version information, then exit.
      
 
      
       -?
       --help
-      Show help, then exit
+      Show help, then exit.
      
 
     
@@ -185,13 +195,6 @@ PostgreSQL documentation
  
   Notes
 
-  
-   pg_rewind requires that the wal_log_hints
-   option is enabled in postgresql.conf, or that data checksums
-   were enabled when the cluster was initialized with initdb.
-   full_page_writes must also be enabled.
-  
-
   
    How it works
 

diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index babeb0269bf45df80f4adc629009138896866230..eb113c2629157e73c284a302a3be037d0231505e 100644 (file)
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -414,8 +414,8 @@ pg_upgrade.exe
     servers
 
     
-     If you have Streaming Replication (
-     linkend="streaming-replication">) or Log-Shipping (
+     If you have Streaming Replication (see 
+     linkend="streaming-replication">) or Log-Shipping (see 
      linkend="warm-standby">) standby servers, follow these steps to
      upgrade them.  You will not be running pg_upgrade
      on the standby servers, but rather rsync.  Do not


diff --git a/doc/src/sgml/ref/vacuumdb.sgml b/doc/src/sgml/ref/vacuumdb.sgml

index e38c34aea37890f57d8a49fd0f87de27715378e2..92b8984b7a6a9db9756ab2176b69841f06485e72 100644 (file)

--- a/doc/src/sgml/ref/vacuumdb.sgml
+++ b/doc/src/sgml/ref/vacuumdb.sgml
@@ -133,6 +133,30 @@ PostgreSQL documentation
       
      
 
+     
+      -j njobs
+      --jobs=njobs
+      
+       
+        Execute the vacuum or analyze commands in parallel by running
+        njobs
+        commands simultaneously.  This option reduces the time of the
+        processing but it also increases the load on the database server.
+       
+       
+        vacuumdb will open
+        njobs connections to the
+        database, so make sure your 
+        setting is high enough to accommodate all connections.
+       
+       
+        Note that using this mode together with the -f
+        (FULL) option might cause deadlock failures if
+        certain system catalogs are processed in parallel.
+       
+      
+     
+
      
       -q
       --quiet
@@ -203,30 +227,6 @@ PostgreSQL documentation
       
      
 
-     
-      -j njobs
-      --jobs=njobs
-      
-       
-        Execute the vacuum or analyze commands in parallel by running
-        njobs
-        commands simultaneously.  This option reduces the time of the
-        processing but it also increases the load on the database server.
-       
-       
-        vacuumdb will open
-        njobs connections to the
-        database, so make sure your 
-        setting is high enough to accommodate all connections.
-       
-       
-        Note that using this mode together with the -f
-        (FULL) option might cause deadlock failures if
-        certain system catalogs are processed in parallel.
-       
-      
-     
-
      
       --analyze-in-stages
       




This is the main PostgreSQL git repository.
RSS
Atom



window.onload = function () {
	var tz_cookie = { name: 'gitweb_tz', expires: 14, path: '/' };
	onloadTZSetup('local', tz_cookie, 'datetime');
};

diff --git a/doc/src/sgml/ref/vacuumdb.sgml b/doc/src/sgml/ref/vacuumdb.sgml
index e38c34aea37890f57d8a49fd0f87de27715378e2..92b8984b7a6a9db9756ab2176b69841f06485e72 100644 (file)
--- a/doc/src/sgml/ref/vacuumdb.sgml
+++ b/doc/src/sgml/ref/vacuumdb.sgml
@@ -133,6 +133,30 @@ PostgreSQL documentation
       
      
 
+     
+      -j njobs
+      --jobs=njobs
+      
+       
+        Execute the vacuum or analyze commands in parallel by running
+        njobs
+        commands simultaneously.  This option reduces the time of the
+        processing but it also increases the load on the database server.
+       
+       
+        vacuumdb will open
+        njobs connections to the
+        database, so make sure your 
+        setting is high enough to accommodate all connections.
+       
+       
+        Note that using this mode together with the -f
+        (FULL) option might cause deadlock failures if
+        certain system catalogs are processed in parallel.
+       
+      
+     
+
      
       -q
       --quiet
@@ -203,30 +227,6 @@ PostgreSQL documentation
       
      
 
-     
-      -j njobs
-      --jobs=njobs
-      
-       
-        Execute the vacuum or analyze commands in parallel by running
-        njobs
-        commands simultaneously.  This option reduces the time of the
-        processing but it also increases the load on the database server.
-       
-       
-        vacuumdb will open
-        njobs connections to the
-        database, so make sure your 
-        setting is high enough to accommodate all connections.
-       
-       
-        Note that using this mode together with the -f
-        (FULL) option might cause deadlock failures if
-        certain system catalogs are processed in parallel.
-       
-      
-     
-
      
       --analyze-in-stages