Improve documentation about CREATE INDEX CONCURRENTLY. Clarify the description of which transactions will block a CREATE INDEX CONCURRENTLY command from proceeding, and mention that the index might still not be usable after CREATE INDEX completes. (This happens if the index build detected broken HOT chains, so that pg_index.indcheckxmin gets set, and there are open old transactions preventing the xmin horizon from advancing past the index's initial creation. I didn't want to explain what broken HOT chains are, though, so I omitted an explanation of exactly when old transactions prevent the index from being used.)
Per discussion with Chris Travers. Back-patch to all supported branches, since the same text appears in all of them. Branch ------ REL9_2_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/528db6ab965d33cfcad7e460b1cc4416f3600c3a Modified Files -------------- doc/src/sgml/ref/create_index.sgml | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
