mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2025-02-23 19:39:53 +08:00
Code Issues Packages Projects Releases Wiki Activity

doc: small fixes for REINDEX reference page

Browse Source 
From: Josh Kupershmidt <schmiddy@gmail.com>
This commit is contained in:
Peter Eisentraut 2014-07-14 20:37:00 -04:00
parent 93c3eca953
commit f7dd97fbae
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/ref/reindex.sgml
View File

@ -46,7 +46,7 @@ REINDEX { INDEX | TABLE | DATABASE | SYSTEM } <replaceable class="PARAMETER">nam
<listitem> <listitem>
<para> <para>
An index has become <quote>bloated</>, that it is contains many An index has become <quote>bloated</>, that is it contains many
empty or nearly-empty pages. This can occur with B-tree indexes in empty or nearly-empty pages. This can occur with B-tree indexes in
<productname>PostgreSQL</productname> under certain uncommon access <productname>PostgreSQL</productname> under certain uncommon access
patterns. <command>REINDEX</command> provides a way to reduce patterns. <command>REINDEX</command> provides a way to reduce
@ -203,7 +203,7 @@ REINDEX { INDEX | TABLE | DATABASE | SYSTEM } <replaceable class="PARAMETER">nam
but not reads of the index's parent table. It also takes an exclusive lock but not reads of the index's parent table. It also takes an exclusive lock
on the specific index being processed, which will block reads that attempt on the specific index being processed, which will block reads that attempt
to use that index. In contrast, <command>DROP INDEX</> momentarily takes to use that index. In contrast, <command>DROP INDEX</> momentarily takes
exclusive lock on the parent table, blocking both writes and reads. The an exclusive lock on the parent table, blocking both writes and reads. The
subsequent <command>CREATE INDEX</> locks out writes but not reads; since subsequent <command>CREATE INDEX</> locks out writes but not reads; since
the index is not there, no read will attempt to use it, meaning that there the index is not there, no read will attempt to use it, meaning that there
will be no blocking but reads might be forced into expensive sequential will be no blocking but reads might be forced into expensive sequential