summaryrefslogtreecommitdiff
path: root/doc
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:40:52 -0400
commitf7dd97fbae69a041cbbbd32196bb24b25f8f7ac5 (patch)
tree5d6eda49bf171a0a1c458497aa44708c96b2bf13 /doc
parent93c3eca9531dfa649d1bf67d727af42a4444312d (diff)
downloadpostgresql-f7dd97fbae69a041cbbbd32196bb24b25f8f7ac5.tar.gz
doc: small fixes for REINDEX reference page
From: Josh Kupershmidt <schmiddy@gmail.com>
Diffstat (limited to 'doc')
-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 722266563e..a795dfa325 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