Re: COPY FREEZE and PD_ALL_VISIBLE

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPY FREEZE and PD_ALL_VISIBLE
Date: 2015-12-24 02:14:09
Message-ID: CAB7nPqRcJC9NVguLVey5GZQKkOt4=4DJpK+EpQWUR3=WAmJNGQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 4, 2015 at 12:08 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> On Tue, Nov 3, 2015 at 8:07 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>>
>> On 3 November 2015 at 15:23, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>>>
>>> On Fri, Oct 23, 2015 at 6:29 AM, Simon Riggs <simon(at)2ndquadrant(dot)com>
>>> wrote:
>>>>
>>>> Easy enough to do it at the end of the COPY FREEZE in one step.
>>>
>>>
>>> Here, we might want to consider that setting bit in visibility map
>>> will generate WAL log whereas Copy Freeze otherwise skip WAL
>>> when wal_level is less than archive. This can lead to extra disk
>>> writes which can slow down Copy Freeze, but OTOH that might
>>> be acceptable.
>>
>>
>> I'm building the map as I go, in the latest version of this patch I'm
>> working on.
>>
>
> As, you are working on this patch, I have marked it as "Waiting on Author".

There has not been an update for this patch in a while, switched to
"returned with feedback" because of lack of author's input.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2015-12-24 02:14:33 Re: Remove Windows crash dump support?
Previous Message David Rowley 2015-12-24 02:12:52 Re: Combining Aggregates