aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2014-07-14 20:37:00 -0400
committerPeter Eisentraut <peter_e@gmx.net>2014-07-14 20:37:00 -0400
commitf162fb75b329bc5370b3ece59f5ef0d5ba0f15d6 (patch)
tree18d0e6114ab9a57221db04c7f8d8654a33a401b0
parentee80f043bc9b92dbbb1ff9577c3c601746124092 (diff)
downloadpostgresql-f162fb75b329bc5370b3ece59f5ef0d5ba0f15d6.tar.gz
postgresql-f162fb75b329bc5370b3ece59f5ef0d5ba0f15d6.zip
doc: small fixes for REINDEX reference page
From: Josh Kupershmidt <schmiddy@gmail.com>
-rw-r--r--doc/src/sgml/ref/reindex.sgml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 3dfaef43f1f..cabae191bc7 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
@@ -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
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