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.
pull/17/merge
Tom Lane 9 years ago
parent 64ee636a5b
commit 39c3ca5161
  1. 4
      doc/src/sgml/release-9.2.sgml
  2. 4
      doc/src/sgml/release-9.3.sgml
  3. 4
      doc/src/sgml/release-9.4.sgml
  4. 4
      doc/src/sgml/release-9.5.sgml
  5. 4
      doc/src/sgml/release-9.6.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

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

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

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

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

Loading…
Cancel
Save