From cd1aae586498a348876b4804bdd1bb7cc743d395 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 7 Sep 2007 00:58:57 +0000 Subject: Allow CREATE INDEX CONCURRENTLY to disregard transactions in other databases, per gripe from hubert depesz lubaczewski. Patch from Simon Riggs. --- doc/src/sgml/ref/create_index.sgml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml index ed2b8e22e70..0fe40c775f8 100644 --- a/doc/src/sgml/ref/create_index.sgml +++ b/doc/src/sgml/ref/create_index.sgml @@ -1,5 +1,5 @@ @@ -308,7 +308,7 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] name @@ -319,7 +319,8 @@ CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] nameCONCURRENTLY option of CREATE INDEX. When this option is used, PostgreSQL must perform two scans of the table, and in - addition it must wait for all existing transactions to terminate. Thus + addition it must wait for all existing transactions that could potentially + use the index to terminate. Thus this method requires more total work than a standard index build and takes significantly longer to complete. However, since it allows normal operations to continue while the index is built, this method is useful for -- cgit v1.2.3