From 38e6eb197d87fc815c88c1caf79cd4cd8887272e Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Sun, 17 Nov 2002 23:43:32 +0000 Subject: [PATCH] Re-order REINDEX options in manual for consistency. REINDEX DATABASE/TABLE/INDEX is the proper order. --- doc/src/sgml/ref/reindex.sgml | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) 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 ] @@ -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 } 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. -- 2.40.0