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

From Andrew Dunstan
Subject Re: 2019-03 CF Summary / Review - Tranche #2
Date
Msg-id f739af83-9a78-b300-3a11-21c4d6524d66@2ndQuadrant.com
Whole thread Raw
In response to Re: 2019-03 CF Summary / Review - Tranche #2  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 2019-03 CF Summary / Review - Tranche #2  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2/18/19 12:43 PM, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
>> On 2019-02-18 12:37:27 -0500, Tom Lane wrote:
>>> Can't you do it now?  The status summary line already shows one
>>> patch as having been pushed to the next CF.
>> 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.


cheers


andrew


-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

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