diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml index 6a927bbbd4..08666b2f02 100644 --- 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 ] @@ -34,14 +34,6 @@ REINDEX { TABLE | DATABASE | INDEX } name - - TABLE - - - Recreate all indexes of a specified table. - - - DATABASE @@ -51,6 +43,14 @@ REINDEX { TABLE | DATABASE | INDEX } name + + TABLE + + + Recreate all indexes of a specified table. + + + INDEX @@ -63,7 +63,7 @@ REINDEX { TABLE | DATABASE | INDEX } namename - 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.