| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Andreas Karlsson <andreas(at)proxel(dot)se>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Commitfest Bug (was: Re: Reusing abbreviated keys during second pass of ordered [set] aggregates) |
| Date: | 2016-02-17 02:19:55 |
| Message-ID: | 56C3D8CB.1010604@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/16/16 12:38 AM, Michael Paquier wrote:
> When a patch with status "Ready for committer" on CF N is moved to CF
> (N+1), its status is automatically changed to "Needs Review". That's
> something to be aware of when cleaning up the CF app entries.
I agree with Alvarro; this seems like a bug to me. If a patch is ready
for committer in CF N, why would it suddenly not be ready in N+1?
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2016-02-17 02:32:47 | Re: [patch] Proposal for \crosstabview in psql |
| Previous Message | Craig Ringer | 2016-02-17 01:37:41 | Re: Re: [COMMITTERS] pgsql: Introduce group locking to prevent parallel processes from deadl |