| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | 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:17:55 |
| Message-ID: | f739af83-9a78-b300-3a11-21c4d6524d66@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/18/19 12:43 PM, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-02-18 23:23:16 | Re: 2019-03 CF Summary / Review - Tranche #2 |
| Previous Message | Tom Lane | 2019-02-18 23:15:00 | Re: Delay locking partitions during INSERT and UPDATE |