Re: [HACKERS] Early locking option to parallel backup - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [HACKERS] Early locking option to parallel backup
Date
Msg-id 20180302193851.74er24c3e6zqkgkr@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] Early locking option to parallel backup  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 2018-03-02 11:42:06 -0500, Robert Haas wrote:
> On Fri, Mar 2, 2018 at 2:29 AM, Andres Freund <andres@anarazel.de> wrote:
> > There seems to to be consensus in this thread that the approach Lucas
> > proposed isn't what we want, and that instead some shared lock based
> > approach is desirable.  As that has been the case for ~1.5 months, I
> > propose we mark this as returned with feedback?
> 
> Yes, that seems pretty clear-cut to me.  It would be totally unfair if
> a patch that hasn't been updated since November were allowed to submit
> a new version after the start of the final CommitFest.  We shouldn't
> be working on anything now that hasn't been under active development
> recently; we have enough things (and then some) that have.

Done.


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [Patch] Checksums for SLRU files
Next
From: Andres Freund
Date:
Subject: Re: 2018-03 Commitfest Summary (Andres #1)