Re: avoid bloat from CREATE INDEX CONCURRENTLY

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: avoid bloat from CREATE INDEX CONCURRENTLY
Date: 2017-02-28 13:05:16
Message-ID: 1884.1488287116@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-02-28 13:17:17 Re: Statement-level rollback
Previous Message Etsuro Fujita 2017-02-28 12:45:22 postgres_fdw: evaluate placeholdervars on remote server