Re-order REINDEX options in manual for consistency. REINDEX

DATABASE/TABLE/INDEX is the proper order.

diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6a927bbbd41f031bbde5a64abf305037708404e0..08666b2f02a2cd8644856fcf7f24775d7cdc28ed 100644 (file)
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -1,5 +1,5 @@
 
 
@@ -21,7 +21,7 @@ PostgreSQL documentation
    2000-03-30
   
   
-REINDEX { TABLE | DATABASE | INDEX } name [ FORCE ]
+REINDEX { DATABASE | TABLE | INDEX } name [ FORCE ]
   
   
   
@@ -35,19 +35,19 @@ REINDEX { TABLE | DATABASE | INDEX } name
 
     
      
-      TABLE
+      DATABASE
       
        
-   Recreate all indexes of a specified table.
+   Recreate all system indexes of a specified database.
+   (User-table indexes are not included.)
        
       
      
      
-      DATABASE
+      TABLE
       
        
-   Recreate all system indexes of a specified database.
-   (User-table indexes are not included.)
+   Recreate all indexes of a specified table.
        
       
      
@@ -63,7 +63,7 @@ REINDEX { TABLE | DATABASE | INDEX } name
       name
       
        
-   The name of the specific table/database/index to be reindexed.
+   The name of the specific database/table/index to be reindexed.
    Table and index names may be schema-qualified.
        
       
@@ -156,8 +156,8 @@ REINDEX
    started instead, giving it
    the command-line options -O and -P (these options allow system table
    modifications and prevent use of system indexes, respectively).  Then
-   issue REINDEX INDEX, REINDEX TABLE, or
-   REINDEX DATABASE depending on how much you want to reconstruct.
+   issue REINDEX DATABASE, REINDEX TABLE, 
+   REINDEX INDEX, or depending on how much you want to reconstruct.
    If in doubt, use REINDEX DATABASE FORCE to force reconstruction
    of all system indexes in the database.  Then quit the standalone backend
    and restart the postmaster.