summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/release-9.2.sgml4
-rw-r--r--doc/src/sgml/release-9.3.sgml4
-rw-r--r--doc/src/sgml/release-9.4.sgml4
3 files changed, 6 insertions, 6 deletions
diff --git a/doc/src/sgml/release-9.2.sgml b/doc/src/sgml/release-9.2.sgml
index 2e24b778a89..9e99de882cf 100644
--- a/doc/src/sgml/release-9.2.sgml
+++ b/doc/src/sgml/release-9.2.sgml
@@ -49,8 +49,8 @@
<para>
If <command>CREATE INDEX CONCURRENTLY</> was used to build an index
- that depends on a column not previously indexed, then rows inserted
- or updated by transactions that ran concurrently with
+ that depends on a column not previously indexed, then rows
+ updated by transactions that ran concurrently with
the <command>CREATE INDEX</> command could have received incorrect
index entries. If you suspect this may have happened, the most
reliable solution is to rebuild affected indexes after installing
diff --git a/doc/src/sgml/release-9.3.sgml b/doc/src/sgml/release-9.3.sgml
index 31adad9d477..19bb305f0e1 100644
--- a/doc/src/sgml/release-9.3.sgml
+++ b/doc/src/sgml/release-9.3.sgml
@@ -49,8 +49,8 @@
<para>
If <command>CREATE INDEX CONCURRENTLY</> was used to build an index
- that depends on a column not previously indexed, then rows inserted
- or updated by transactions that ran concurrently with
+ that depends on a column not previously indexed, then rows
+ updated by transactions that ran concurrently with
the <command>CREATE INDEX</> command could have received incorrect
index entries. If you suspect this may have happened, the most
reliable solution is to rebuild affected indexes after installing
diff --git a/doc/src/sgml/release-9.4.sgml b/doc/src/sgml/release-9.4.sgml
index b4e64214ad7..bbf2429475c 100644
--- a/doc/src/sgml/release-9.4.sgml
+++ b/doc/src/sgml/release-9.4.sgml
@@ -48,8 +48,8 @@
<para>
If <command>CREATE INDEX CONCURRENTLY</> was used to build an index
- that depends on a column not previously indexed, then rows inserted
- or updated by transactions that ran concurrently with
+ that depends on a column not previously indexed, then rows
+ updated by transactions that ran concurrently with
the <command>CREATE INDEX</> command could have received incorrect
index entries. If you suspect this may have happened, the most
reliable solution is to rebuild affected indexes after installing