Call out vacuum considerations in create index docs

Backpatch to pg12, which is as far as it goes without conflicts.

Author: James Coleman 
Reviewed-by: "David G. Johnston" 
Discussion: https://postgr.es/m/CAAaqYe9oEfbz7AxXq7OX+FFVi5w5p1e_Of8ON8ZnKO9QqBfmjg@mail.gmail.com

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 6fff02d82430293b6574b67d368518e10be660a0..a5271a9f8f2e20fc0e3e6b63a29a529999dfb80d 100644 (file)
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -851,6 +851,12 @@ Indexes:
    to remove an index.
   
 
+  
+   Like any long-running transaction, CREATE INDEX on a
+   table can affect which tuples can be removed by concurrent
+   VACUUM on any other table.
+  
+
   
    Prior releases of PostgreSQL also had an
    R-tree index method.  This method has been removed because

diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
index 6e1cf067130c924947e750231ac7a76f70801c3c..627b36300c984df281092d4447d0d7873e4d1794 100644 (file)
--- a/doc/src/sgml/ref/reindex.sgml
+++ b/doc/src/sgml/ref/reindex.sgml
@@ -436,6 +436,12 @@ Indexes:
     CONCURRENTLY cannot.
    
 
+   
+    Like any long-running transaction, REINDEX on a table
+    can affect which tuples can be removed by concurrent
+    VACUUM on any other table.
+   
+
    
     REINDEX SYSTEM does not support
     CONCURRENTLY since system catalogs cannot be reindexed