Alvaro Herrera <alvhe...@2ndquadrant.com> writes: > This patch reduces the amount of bloat you get from running CREATE INDEX > CONCURRENTLY by destroying the snapshot taken in the first phase, before > entering the second phase. This allows the global xmin to advance,
Um ... isn't there a transaction boundary there anyway?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
