Re: COPY FREEZE and PD_ALL_VISIBLE
| От | Amit Kapila |
|---|---|
| Тема | Re: COPY FREEZE and PD_ALL_VISIBLE |
| Дата | |
| Msg-id | CAA4eK1LfvBfSrBWGhZ5TA1puuoenf0UG36hW=BvjD4S0y1Eggw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: COPY FREEZE and PD_ALL_VISIBLE (Simon Riggs <simon@2ndQuadrant.com>) |
| Ответы |
Re: COPY FREEZE and PD_ALL_VISIBLE
|
| Список | pgsql-hackers |
On Tue, Nov 3, 2015 at 8:07 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
>
> On 3 November 2015 at 15:23, Amit Kapila <amit.kapila16@gmail.com> wrote:
>>
>> On Fri, Oct 23, 2015 at 6:29 AM, Simon Riggs <simon@2ndquadrant.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.
>
>
> On 3 November 2015 at 15:23, Amit Kapila <amit.kapila16@gmail.com> wrote:
>>
>> On Fri, Oct 23, 2015 at 6:29 AM, Simon Riggs <simon@2ndquadrant.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".
В списке pgsql-hackers по дате отправления: