Re: 2019-03 CF Summary / Review - Tranche #2 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: 2019-03 CF Summary / Review - Tranche #2
Date
Msg-id 10816.1550532196@sss.pgh.pa.us
Whole thread Raw
In response to Re: 2019-03 CF Summary / Review - Tranche #2  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: 2019-03 CF Summary / Review - Tranche #2  (David Steele <david@pgmasters.net>)
List pgsql-hackers
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> On 2/18/19 12:43 PM, Tom Lane wrote:
>> Andres Freund <andres@anarazel.de> writes:
>>> It's CF app nannyism. One can't move a patch to the next CF that's
>>> waiting-on-author. I've complained about that a number of times, but...

>> So change it to another state, push it, change it again.

> I'm with Andres. I found this annoying six months ago.

Oh, I agree the restriction is stupid.  I'm just pointing out that
it can be gotten around.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: 2019-03 CF Summary / Review - Tranche #2
Next
From: David Rowley
Date:
Subject: Re: Delay locking partitions during INSERT and UPDATE