diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-02-07 10:24:25 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-02-07 10:24:51 -0500 |
| commit | 903bfef382f286a75e82b8b9edd93b2bdc6cfd96 (patch) | |
| tree | 4dd9357bfa6cd6d86e118ce2eaaddb5f8570463c | |
| parent | 0021ce274319215fdc481ae29f059068f7a5bf0a (diff) | |
| download | postgresql-903bfef382f286a75e82b8b9edd93b2bdc6cfd96.tar.gz postgresql-903bfef382f286a75e82b8b9edd93b2bdc6cfd96.zip | |
Correct thinko in last-minute release note item.REL9_2_20
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.sgml | 4 |
1 files changed, 2 insertions, 2 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 |