| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: avoid bloat from CREATE INDEX CONCURRENTLY |
| Date: | 2017-02-28 13:23:05 |
| Message-ID: | CANP8+j+2b4D9rGz_WDEka-6+=Uu=9QF5nCERV7yJ2b3VSZ=JaQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 28 February 2017 at 13:05, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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?
Yes, the patch releases the snapshot early, so it does not hold it
once the build scan has completed. This allows the sort and build
phases to occur without holding back the xmin.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Michálek | 2017-02-28 13:23:56 | Re: Other formats in pset like markdown, rst, mediawiki |
| Previous Message | David Steele | 2017-02-28 13:21:18 | Re: Backend crash on non-exclusive backup cancel |