Minor re-wording following recent locking changes.
--
Best Regards, Simon Riggs
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/ref/reindex.sgml,v
retrieving revision 1.24
diff -d -c -r1.24 reindex.sgml
*** reindex.sgml 24 Oct 2004 22:52:04 -0000 1.24
--- reindex.sgml 4 Nov 2004 15:04:30 -0000
***************
*** 119,131 ****
<para>
If you suspect corruption of an index on a user table, you can
simply rebuild that index, or all indexes on the table, using
! <command>REINDEX INDEX</command> or <command>REINDEX
! TABLE</command>. Another approach to dealing with a corrupted
! user-table index is just to drop and recreate it. This may in fact
! be preferable if you would like to maintain some semblance of
! normal operation on the table meanwhile. <command>REINDEX</>
! acquires exclusive lock on the table, while <command>CREATE
! INDEX</> only locks out writes not reads of the table.
</para>
<para>
--- 119,128 ----
<para>
If you suspect corruption of an index on a user table, you can
simply rebuild that index, or all indexes on the table, using
! <command>REINDEX INDEX</command> or <command>REINDEX TABLE</command>.
! This is equivalent to a drop and recreate of the user-table index.
! <command>REINDEX</> locks out writes not reads on the table, plus
! an exclusive lock on the specific index being processed.
</para>
<para>
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
