summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-02-07 10:24:25 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2017-02-07 10:24:25 -0500
commitcd898769cb6635a7440ebbabe15f7ecbf5157d68 (patch)
tree1fc9a9d1cf53fd6b8d4ba8ad4cd93d9b22b2ea4e
parent01306452b1481a73a24fe7396f84797d37269865 (diff)
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.
-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