Correction on CREATE INDEX CONCURRENTLY description for 20170209 release

diff --git a/update_releases/current/20170209updaterelease.md b/update_releases/current/20170209updaterelease.md
index 0cccb8986c08527f65f13d704a78c36bb8de7fef..7d0b9acca43d51f22bc93c02c76963e772445e70 100644 (file)
--- 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 7a7db12f75c33e6e680afb320cb4411ca2c1b99f..c15d8942aa64908b7951f6faf265e885861e6faa 100644 (file)
--- 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.