Re: 2019-03 CF Summary / Review - Tranche #2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, David Steele <david(at)pgmasters(dot)net>, pgsql-hackers(at)postgresql(dot)org, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: 2019-03 CF Summary / Review - Tranche #2
Date: 2019-02-18 23:23:16
Message-ID: 10816.1550532196@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> On 2/18/19 12:43 PM, Tom Lane wrote:
>> Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2019-02-18 23:28:32 Re: Delay locking partitions during INSERT and UPDATE
Previous Message Andrew Dunstan 2019-02-18 23:17:55 Re: 2019-03 CF Summary / Review - Tranche #2