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.

diff --git a/doc/src/sgml/release-9.2.sgml b/doc/src/sgml/release-9.2.sgml
index 2e24b778a894426cc81356a78b53fbbd347defe4..9e99de882cf8c1210d3b74f587621902d8cbb17d 100644 (file)
--- 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

diff --git a/doc/src/sgml/release-9.3.sgml b/doc/src/sgml/release-9.3.sgml
index 31adad9d4772aa8d3f2ef2bd4decdc4eb90b0d66..19bb305f0e1e84eb7dcf9f295c67b7c16ba508de 100644 (file)
--- a/doc/src/sgml/release-9.3.sgml
+++ b/doc/src/sgml/release-9.3.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