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:25 -0500 |
| commit | 4dd4e3fe10a9d85d5a1455b2231daae8c00c6b79 (patch) | |
| tree | 0ec9734c98d8ab6a49263d684c87b9f3ec1467a1 | |
| parent | 6f5e8094c2c0b829e3d00fc1e1656248457e16e6 (diff) | |
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.
| -rw-r--r-- | doc/src/sgml/release-9.2.sgml | 4 | ||||
| -rw-r--r-- | doc/src/sgml/release-9.3.sgml | 4 |
2 files changed, 4 insertions, 4 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 diff --git a/doc/src/sgml/release-9.3.sgml b/doc/src/sgml/release-9.3.sgml index 31adad9d477..19bb305f0e1 100644 --- a/doc/src/sgml/release-9.3.sgml +++ b/doc/src/sgml/release-9.3.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 |