rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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.
This commit is contained in:
Tom Lane 2017-02-07 10:24:24 -05:00
parent 64ee636a5b
commit 39c3ca5161
5 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/release-9.2.sgml
View File

@ -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

4
doc/src/sgml/release-9.3.sgml
View File

@ -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

4
doc/src/sgml/release-9.4.sgml
View File

@ -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

4
doc/src/sgml/release-9.5.sgml
View File

@ -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

4
doc/src/sgml/release-9.6.sgml
View File

@ -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