database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-29 16:21:20 +03:00
Code

Correct thinko in last-minute release note item.

Browse Source 
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:25 -05:00
parent 6f5e8094c2
commit 4dd4e3fe10
2 changed files with 4 additions and 4 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