From 903bfef382f286a75e82b8b9edd93b2bdc6cfd96 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Tue, 7 Feb 2017 10:24:25 -0500 Subject: [PATCH] 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. --- doc/src/sgml/release-9.2.sgml | 4 ++-- 1 file 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 @@ If 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 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