Re: Improving replay of XLOG_BTREE_VACUUM records

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Vladimir Borodin <root(at)simply(dot)name>, David Steele <david(at)pgmasters(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improving replay of XLOG_BTREE_VACUUM records
Date: 2016-03-11 09:36:31
Message-ID: CANP8+jL3EFAQuRPnb7Vki9N3sX5cH1TAvCtCFVAi0o0udgcsZQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10 March 2016 at 11:38, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:

> On 10 March 2016 at 09:22, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
> wrote:
>
>> On Thu, Mar 10, 2016 at 10:00 AM, Vladimir Borodin <root(at)simply(dot)name>
>> wrote:
>> > Let’s do immediately after you will send a new version of your patch? Or
>> > even better after testing your patch? Don’t get me wrong, but rejecting
>> my
>> > patch without tangible work on your patch may lead to forgiving about
>> the
>> > problem before 9.6 freeze.
>>
>> This makes sense. Let's not reject this patch yet if the alternative
>> approach is not committed.
>>
>
> I attach 2 patches.
>

I'll wait for review, so setting status back to Needs Review.

Assuming review, I will commit the week w/c 21 March.

--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Shulgin, Oleksandr 2016-03-11 09:49:15 Re: Patch to implement pg_current_logfile() function
Previous Message Oleg Bartunov 2016-03-11 09:19:16 Re: The plan for FDW-based sharding