From 93c39f987e9c019cd28c450ece8a621b2d8ce28a Mon Sep 17 00:00:00 2001 From: Alvaro Herrera Date: Wed, 13 Jan 2021 17:55:41 -0300 Subject: [PATCH] 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 --- doc/src/sgml/ref/create_index.sgml | 6 ++++++ doc/src/sgml/ref/reindex.sgml | 6 ++++++ 2 files changed, 12 insertions(+) diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml index 6fff02d824..a5271a9f8f 100644 --- 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 6e1cf06713..627b36300c 100644 --- 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