From 187b75bd106dde758f9518cb49837f6baddd054e Mon Sep 17 00:00:00 2001 From: "Jonathan S. Katz" Date: Tue, 7 Feb 2017 10:22:17 -0500 Subject: [PATCH] Correction on CREATE INDEX CONCURRENTLY description for 20170209 release --- update_releases/current/20170209updaterelease.md | 2 +- update_releases/current/20170209updaterelease.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/update_releases/current/20170209updaterelease.md b/update_releases/current/20170209updaterelease.md index 0cccb89..7d0b9ac 100644 --- a/update_releases/current/20170209updaterelease.md +++ b/update_releases/current/20170209updaterelease.md @@ -8,7 +8,7 @@ Users should plan to apply this update at the next scheduled downtime. Build corruption with CREATE INDEX CONCURRENTLY ---------------------------------- -There existed a race condition if CREATE INDEX CONCURRENTLY was called on a column that had not been indexed before, then rows that were inserted or updated by transactions running at the same time as the CREATE INDEX CONCURRENTLY command could have been index incorrectly. +There existed a race condition if CREATE INDEX CONCURRENTLY was called on a column that had not been indexed before, then rows that were updated by transactions running at the same time as the CREATE INDEX CONCURRENTLY command could have been index incorrectly. If you suspect this may have happened, the most reliable solution is to rebuild affected indexes after installing this update. diff --git a/update_releases/current/20170209updaterelease.txt b/update_releases/current/20170209updaterelease.txt index 7a7db12..c15d894 100644 --- a/update_releases/current/20170209updaterelease.txt +++ b/update_releases/current/20170209updaterelease.txt @@ -8,7 +8,7 @@ Users should plan to apply this update at the next scheduled downtime. Build corruption with CREATE INDEX CONCURRENTLY ---------------------------------- -There existed a race condition if CREATE INDEX CONCURRENTLY was called on a column that had not been indexed before, then rows that were inserted or updated by transactions running at the same time as the CREATE INDEX CONCURRENTLY command could have been index incorrectly. +There existed a race condition if CREATE INDEX CONCURRENTLY was called on a column that had not been indexed before, then rows that were updated by transactions running at the same time as the CREATE INDEX CONCURRENTLY command could have been index incorrectly. If you suspect this may have happened, the most reliable solution is to rebuild affected indexes after installing this update. -- 2.39.5