Thanks to visit codestin.com
Credit goes to postgrespro.com

Re: Improving replay of XLOG_BTREE_VACUUM records - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Improving replay of XLOG_BTREE_VACUUM records
Date
Msg-id CAB7nPqQCsZWsw5WVB2RsaHAQPDa6L5xHgiEC-BDsq68nZvGThw@mail.gmail.com
Whole thread Raw
In response to Re: Improving replay of XLOG_BTREE_VACUUM records  (Vladimir Borodin <[email protected]>)
Responses Re: Improving replay of XLOG_BTREE_VACUUM records
List pgsql-hackers
On Thu, Mar 10, 2016 at 10:00 AM, Vladimir Borodin <[email protected]> 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.
--
Michael



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Small patch for pgstat.c: fix comment + pgindent
Next
From: Amit Kapila
Date:
Subject: Re: Explain [Analyze] produces parallel scan for select Into table statements.