diff options
| author | Peter Eisentraut | 2014-07-15 00:37:00 +0000 |
|---|---|---|
| committer | Peter Eisentraut | 2014-07-15 00:42:16 +0000 |
| commit | bae0b5c42d896643b8625d044916b18a204e4416 (patch) | |
| tree | fdd017c9ada86df50820ae8931e1c9864a28b302 | |
| parent | 77b55869475e1f7dc77d484b7ea5b109e919a818 (diff) | |
doc: small fixes for REINDEX reference page
From: Josh Kupershmidt <[email protected]>
| -rw-r--r-- | doc/src/sgml/ref/reindex.sgml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml index b4b1466f5ca..bc6b72bccd4 100644 --- a/doc/src/sgml/ref/reindex.sgml +++ b/doc/src/sgml/ref/reindex.sgml @@ -46,7 +46,7 @@ REINDEX { INDEX | TABLE | DATABASE | SYSTEM } <replaceable class="PARAMETER">nam <listitem> <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 <productname>PostgreSQL</productname> under certain uncommon access patterns. <command>REINDEX</command> provides a way to reduce @@ -228,7 +228,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 on the specific index being processed, which will block reads that attempt 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 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 |