From ae8a602c32f839af8e467230fedb8e0c48540666 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Tue, 7 Feb 2017 10:24:25 -0500
Subject: [PATCH] Correct thinko in last-minute release note item.
The CREATE INDEX CONCURRENTLY bug can only be triggered by row updates,
not inserts, since the problem would arise from an update incorrectly
being made HOT. Noted by Alvaro.
---
doc/src/sgml/release-9.2.sgml | 4 ++--
doc/src/sgml/release-9.3.sgml | 4 ++--
doc/src/sgml/release-9.4.sgml | 4 ++--
doc/src/sgml/release-9.5.sgml | 4 ++--
doc/src/sgml/release-9.6.sgml | 4 ++--
5 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/doc/src/sgml/release-9.2.sgml b/doc/src/sgml/release-9.2.sgml
index 2e24b778a8..9e99de882c 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 31adad9d47..19bb305f0e 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 b4e64214ad..bbf2429475 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
diff --git a/doc/src/sgml/release-9.5.sgml b/doc/src/sgml/release-9.5.sgml
index 2438b95b8c..aab3ddc3c1 100644
--- a/doc/src/sgml/release-9.5.sgml
+++ b/doc/src/sgml/release-9.5.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
diff --git a/doc/src/sgml/release-9.6.sgml b/doc/src/sgml/release-9.6.sgml
index ea46bdb5d4..bffcaac46e 100644
--- a/doc/src/sgml/release-9.6.sgml
+++ b/doc/src/sgml/release-9.6.sgml
@@ -57,8 +57,8 @@ Branch: REL9_2_STABLE [bcd7b47c2] 2017-02-06 13:20:25 -0500
<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
--
2.40.0