mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-12-21 08:29:39 +08:00
Re-order REINDEX options in manual for consistency. REINDEX
DATABASE/TABLE/INDEX is the proper order.
This commit is contained in:
parent
8fbef3b55d
commit
38e6eb197d
@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/reindex.sgml,v 1.13 2002/09/21 18:32:54 petere Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/ref/reindex.sgml,v 1.14 2002/11/17 23:43:32 momjian Exp $
|
||||
PostgreSQL documentation
|
||||
-->
|
||||
|
||||
@ -21,7 +21,7 @@ PostgreSQL documentation
|
||||
<date>2000-03-30</date>
|
||||
</refsynopsisdivinfo>
|
||||
<synopsis>
|
||||
REINDEX { TABLE | DATABASE | INDEX } <replaceable class="PARAMETER">name</replaceable> [ FORCE ]
|
||||
REINDEX { DATABASE | TABLE | INDEX } <replaceable class="PARAMETER">name</replaceable> [ FORCE ]
|
||||
</synopsis>
|
||||
|
||||
<refsect2 id="R2-SQL-REINDEX-1">
|
||||
@ -34,14 +34,6 @@ REINDEX { TABLE | DATABASE | INDEX } <replaceable class="PARAMETER">name</replac
|
||||
<para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>TABLE</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Recreate all indexes of a specified table.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>DATABASE</term>
|
||||
<listitem>
|
||||
@ -51,6 +43,14 @@ REINDEX { TABLE | DATABASE | INDEX } <replaceable class="PARAMETER">name</replac
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>TABLE</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Recreate all indexes of a specified table.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>INDEX</term>
|
||||
<listitem>
|
||||
@ -63,7 +63,7 @@ REINDEX { TABLE | DATABASE | INDEX } <replaceable class="PARAMETER">name</replac
|
||||
<term><replaceable class="PARAMETER">name</replaceable></term>
|
||||
<listitem>
|
||||
<para>
|
||||
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.
|
||||
</para>
|
||||
</listitem>
|
||||
@ -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 <command>REINDEX INDEX</>, <command>REINDEX TABLE</>, or
|
||||
<command>REINDEX DATABASE</> depending on how much you want to reconstruct.
|
||||
issue <command>REINDEX DATABASE</>, <command>REINDEX TABLE</>,
|
||||
<command>REINDEX INDEX</>, or depending on how much you want to reconstruct.
|
||||
If in doubt, use <command>REINDEX DATABASE FORCE</> to force reconstruction
|
||||
of all system indexes in the database. Then quit the standalone backend
|
||||
and restart the postmaster.
|
||||
|
Loading…
Reference in New Issue
Block a user