Some reference page improvements

initdb: Add -T option
oid2name: Put options in some non-random order
pg_dump: Put --section option in the right place

And some additional markup and terminology improvements.

diff --git a/doc/src/sgml/oid2name.sgml b/doc/src/sgml/oid2name.sgml
index a4c83925abac72d533e42d8200edf1c03d658053..30e8bb1972c67d45a14d28a00eb19a7e1762e8e4 100644 (file)
--- a/doc/src/sgml/oid2name.sgml
+++ b/doc/src/sgml/oid2name.sgml
@@ -60,18 +60,23 @@
    
 
     
-     -o oid
-     show info for table with OID oid
+     -f filenode
+     show info for table with filenode filenode
     
 
     
-     -f filenode>
-     show info for table with filenode filenode
+     -i>
+     include indexes and sequences in the listing
     
 
     
-     -t tablename_pattern
-     show info for table(s) matching tablename_pattern
+     -o oid
+     show info for table with OID oid
+    
+
+    
+     -q
+     omit headers (useful for scripting)
     
 
     
@@ -88,8 +93,8 @@
     
 
     
-     -i>
-     include indexes and sequences in the listing
+     -t tablename_pattern>
+     show info for table(s) matching tablename_pattern
     
 
     
@@ -98,12 +103,14 @@
       schema name, and OID
      
     
+   
+  
 
-    
-     -q
-     omit headers (useful for scripting)
-    
+  
+   oid2name also accepts the following command-line
+   arguments for connection parameters:
 
+   
     
      -d database
      database to connect to

diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml
index 89f392eaeb04e00c9fc0d85042296ed7fdb4f7a2..b2e94e83d8e00cd5b053f42db0b0a9ddd7de5918 100644 (file)
--- a/doc/src/sgml/ref/initdb.sgml
+++ b/doc/src/sgml/ref/initdb.sgml
@@ -230,6 +230,7 @@ PostgreSQL documentation
      
 
      
+      -T CFG
       --text-search-config=CFG
       
        
@@ -283,7 +284,7 @@ PostgreSQL documentation
    
 
    
-    Other, less commonly used, parameters are also available:
+    Other, less commonly used, options are also available:
 
     
      

diff --git a/doc/src/sgml/ref/pg_basebackup.sgml b/doc/src/sgml/ref/pg_basebackup.sgml
index 7e343e671b658cb97186c5e0324cd7dfb2056dbf..76bfcf1cbb854145333e5757373ef942613b8a83 100644 (file)
--- a/doc/src/sgml/ref/pg_basebackup.sgml
+++ b/doc/src/sgml/ref/pg_basebackup.sgml
@@ -129,7 +129,7 @@ PostgreSQL documentation
         stdout.
        
        
-        This parameter is required.
+        This option is required.
        
       
      
@@ -420,7 +420,7 @@ PostgreSQL documentation
    
 
    
-    Other, less commonly used, parameters are also available:
+    Other, less commonly used, options are also available:
 
     
      

diff --git a/doc/src/sgml/ref/pg_controldata.sgml b/doc/src/sgml/ref/pg_controldata.sgml
index 7926acb918083ca61edcad4f56ce2029b7b1e523..c9eebc089e6c88bbee47f1ee1339b8c052665cba 100644 (file)
--- a/doc/src/sgml/ref/pg_controldata.sgml
+++ b/doc/src/sgml/ref/pg_controldata.sgml
@@ -42,9 +42,9 @@ PostgreSQL documentation
    it requires read access to the data directory.
    You can specify the data directory on the command line, or use
    the environment variable PGDATA.  This utility supports the options
-   <literal>-V and >--version, which print the
+   <option>-V and >--version, which print the
    pg_controldata version and exit.  It also
-   supports options <literal>-? and >--help, which output the
+   supports options <option>-? and >--help, which output the
    supported arguments.
   
  

diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index 4f7f5109fb9dc979196e86a7e437e39c600433eb..12ddd2596621781762ce251f8a587696f237617c 100644 (file)
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -413,22 +413,6 @@ PostgreSQL documentation
       
      
 
-     
-       --section=sectionname
-       
-         
-           Only dump the named section. The name can be one of pre-data, data
-           and post-data.
-           This option can be specified more than once. The default is to dump all sections.
-         
-         
-           Post-data items consist of definitions of indexes, triggers, rules
-           and constraints other than validated check constraints.
-           Pre-data items consist of all other data definition items.
-         
-       
-     
-
      
       -S username
       --superuser=username
@@ -734,6 +718,22 @@ PostgreSQL documentation
       
      
 
+     
+       --section=sectionname
+       
+         
+           Only dump the named section. The name can be one of pre-data, data
+           and post-data.
+           This option can be specified more than once. The default is to dump all sections.
+         
+         
+           Post-data items consist of definitions of indexes, triggers, rules
+           and constraints other than validated check constraints.
+           Pre-data items consist of all other data definition items.
+         
+       
+     
+
      
       --serializable-deferrable
       

diff --git a/doc/src/sgml/ref/pg_receivexlog.sgml b/doc/src/sgml/ref/pg_receivexlog.sgml
index 07f64181c1f2358b80655a98aa50f427553fee5c..8e5fca402281e91551ea217e6378b4a87fffd74e 100644 (file)
--- a/doc/src/sgml/ref/pg_receivexlog.sgml
+++ b/doc/src/sgml/ref/pg_receivexlog.sgml
@@ -192,7 +192,7 @@ PostgreSQL documentation
    
 
    
-    Other, less commonly used, parameters are also available:
+    Other, less commonly used, options are also available:
 
     
      

diff --git a/doc/src/sgml/ref/pg_resetxlog.sgml b/doc/src/sgml/ref/pg_resetxlog.sgml
index fe67a3d1f20f467c62d779a8b3cf4985fed84eea..e98ae4044599f46de0250ce7cd59b282bfa315fb 100644 (file)
--- a/doc/src/sgml/ref/pg_resetxlog.sgml
+++ b/doc/src/sgml/ref/pg_resetxlog.sgml
@@ -63,13 +63,13 @@ PostgreSQL documentation
   
    If pg_resetxlog complains that it cannot determine
    valid data for pg_control, you can force it to proceed anyway
-   by specifying the <literal>-f (force) switch.  In this case plausible
+   by specifying the <option>-f (force) option.  In this case plausible
    values will be substituted for the missing data.  Most of the fields can be
    expected to match, but manual assistance might be needed for the next OID,
    next transaction ID and epoch, next multitransaction ID and offset, and
-   WAL starting address fields. These fields can be set using the switches
+   WAL starting address fields. These fields can be set using the options
    discussed below. If you are not able to determine correct values for all
-   these fields, <literal>-f can still be used, but
+   these fields, <option>-f can still be used, but
    the recovered database must be treated with even more suspicion than
    usual: an immediate dump and reload is imperative.  Do not
    execute any data-modifying operations in the database before you dump,
@@ -77,10 +77,10 @@ PostgreSQL documentation
   
 
   
-   The <literal>-o, -x, >-e,
-   <literal>-m, >-O,
-   and <literal>-l
-   switches allow the next OID, next transaction ID, next transaction ID's
+   The <option>-o, -x, >-e,
+   <option>-m, >-O,
+   and <option>-l
+   options allow the next OID, next transaction ID, next transaction ID's
    epoch, next multitransaction ID, next multitransaction offset, and WAL
    starting address values to be set manually.  These are only needed when
    pg_resetxlog is unable to determine appropriate values
@@ -90,12 +90,12 @@ PostgreSQL documentation
    
     
      
-      A safe value for the next transaction ID (<literal>-x)
+      A safe value for the next transaction ID (<option>-x)
       can be determined by looking for the numerically largest
       file name in the directory pg_clog under the data directory,
       adding one,
       and then multiplying by 1048576.  Note that the file names are in
-      hexadecimal.  It is usually easiest to specify the switch value in
+      hexadecimal.  It is usually easiest to specify the option value in
       hexadecimal too. For example, if 0011 is the largest entry
       in pg_clog, -x 0x1200000 will work (five
       trailing zeroes provide the proper multiplier).
@@ -104,29 +104,29 @@ PostgreSQL documentation
 
     
      
-      A safe value for the next multitransaction ID (<literal>-m)
+      A safe value for the next multitransaction ID (<option>-m)
       can be determined by looking for the numerically largest
       file name in the directory pg_multixact/offsets under the
       data directory, adding one, and then multiplying by 65536.  As above,
       the file names are in hexadecimal, so the easiest way to do this is to
-      specify the switch value in hexadecimal and add four zeroes.
+      specify the option value in hexadecimal and add four zeroes.
      
     
 
     
      
-      A safe value for the next multitransaction offset (<literal>-O)
+      A safe value for the next multitransaction offset (<option>-O)
       can be determined by looking for the numerically largest
       file name in the directory pg_multixact/members under the
       data directory, adding one, and then multiplying by 65536.  As above,
       the file names are in hexadecimal, so the easiest way to do this is to
-      specify the switch value in hexadecimal and add four zeroes.
+      specify the option value in hexadecimal and add four zeroes.
      
     
 
     
      
-      The WAL starting address (<literal>-l) should be
+      The WAL starting address (<option>-l) should be
       larger than any WAL segment file name currently existing in
       the directory pg_xlog under the data directory.
       These names are also in hexadecimal and have three parts.  The first
@@ -143,9 +143,9 @@ PostgreSQL documentation
      
       
        pg_resetxlog itself looks at the files in
-       pg_xlog and chooses a default <literal>-l setting
+       pg_xlog and chooses a default <option>-l setting
        beyond the last existing file name.  Therefore, manual adjustment of
-       <literal>-l should only be needed if you are aware of WAL segment
+       <option>-l should only be needed if you are aware of WAL segment
        files that are not currently present in pg_xlog, such as
        entries in an offline archive; or if the contents of
        pg_xlog have been lost entirely.
@@ -176,7 +176,7 @@ PostgreSQL documentation
   
 
   
-   The <literal>-n (no operation) switch instructs
+   The <option>-n (no operation) option instructs
    pg_resetxlog to print the values reconstructed from
    pg_control and then exit without modifying anything.
    This is mainly a debugging tool, but can be useful as a sanity check
@@ -184,9 +184,9 @@ PostgreSQL documentation
   
 
   
-   The <literal>-V and >--version options print
+   The <option>-V and >--version options print
    the pg_resetxlog version and exit.  The
-   options <literal>-? and >--help show supported arguments,
+   options <option>-? and >--help show supported arguments,
    and exit.