Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit ae8a602

Browse files
committed
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.
1 parent 6a18e4b commit ae8a602

File tree

5 files changed

+10
-10
lines changed

5 files changed

+10
-10
lines changed

doc/src/sgml/release-9.2.sgml

+2-2
Original file line numberDiff line numberDiff line change
@@ -49,8 +49,8 @@
4949

5050
<para>
5151
If <command>CREATE INDEX CONCURRENTLY</> was used to build an index
52-
that depends on a column not previously indexed, then rows inserted
53-
or updated by transactions that ran concurrently with
52+
that depends on a column not previously indexed, then rows
53+
updated by transactions that ran concurrently with
5454
the <command>CREATE INDEX</> command could have received incorrect
5555
index entries. If you suspect this may have happened, the most
5656
reliable solution is to rebuild affected indexes after installing

doc/src/sgml/release-9.3.sgml

+2-2
Original file line numberDiff line numberDiff line change
@@ -49,8 +49,8 @@
4949

5050
<para>
5151
If <command>CREATE INDEX CONCURRENTLY</> was used to build an index
52-
that depends on a column not previously indexed, then rows inserted
53-
or updated by transactions that ran concurrently with
52+
that depends on a column not previously indexed, then rows
53+
updated by transactions that ran concurrently with
5454
the <command>CREATE INDEX</> command could have received incorrect
5555
index entries. If you suspect this may have happened, the most
5656
reliable solution is to rebuild affected indexes after installing

doc/src/sgml/release-9.4.sgml

+2-2
Original file line numberDiff line numberDiff line change
@@ -48,8 +48,8 @@
4848

4949
<para>
5050
If <command>CREATE INDEX CONCURRENTLY</> was used to build an index
51-
that depends on a column not previously indexed, then rows inserted
52-
or updated by transactions that ran concurrently with
51+
that depends on a column not previously indexed, then rows
52+
updated by transactions that ran concurrently with
5353
the <command>CREATE INDEX</> command could have received incorrect
5454
index entries. If you suspect this may have happened, the most
5555
reliable solution is to rebuild affected indexes after installing

doc/src/sgml/release-9.5.sgml

+2-2
Original file line numberDiff line numberDiff line change
@@ -48,8 +48,8 @@
4848

4949
<para>
5050
If <command>CREATE INDEX CONCURRENTLY</> was used to build an index
51-
that depends on a column not previously indexed, then rows inserted
52-
or updated by transactions that ran concurrently with
51+
that depends on a column not previously indexed, then rows
52+
updated by transactions that ran concurrently with
5353
the <command>CREATE INDEX</> command could have received incorrect
5454
index entries. If you suspect this may have happened, the most
5555
reliable solution is to rebuild affected indexes after installing

doc/src/sgml/release-9.6.sgml

+2-2
Original file line numberDiff line numberDiff line change
@@ -57,8 +57,8 @@ Branch: REL9_2_STABLE [bcd7b47c2] 2017-02-06 13:20:25 -0500
5757

5858
<para>
5959
If <command>CREATE INDEX CONCURRENTLY</> was used to build an index
60-
that depends on a column not previously indexed, then rows inserted
61-
or updated by transactions that ran concurrently with
60+
that depends on a column not previously indexed, then rows
61+
updated by transactions that ran concurrently with
6262
the <command>CREATE INDEX</> command could have received incorrect
6363
index entries. If you suspect this may have happened, the most
6464
reliable solution is to rebuild affected indexes after installing

0 commit comments

Comments
 (0)