| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | 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-11-04 03:08:30 |
| Message-ID: | CAA4eK1LfvBfSrBWGhZ5TA1puuoenf0UG36hW=BvjD4S0y1Eggw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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".
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-11-04 03:10:08 | Re: Trivial heap_finish_speculative() error message inaccuracy |
| Previous Message | Ashutosh Bapat | 2015-11-04 03:03:21 | Re: Getting sorted data from foreign server |