Postgres Pro
Downloads
Home   >   mailing lists

Commitfest Bug (was: Re: Reusing abbreviated keys during second pass of ordered [set] aggregates) - Mailing list pgsql-hackers

From Jim Nasby
Subject Commitfest Bug (was: Re: Reusing abbreviated keys during second pass of ordered [set] aggregates)
Date
Msg-id 56C3D8CB.1010604@BlueTreble.com
Whole thread Raw
In response to Re: Re: Reusing abbreviated keys during second pass of ordered [set] aggregates  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Commitfest Bug (was: Re: Reusing abbreviated keys during second pass of ordered [set] aggregates)
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Introduce group locking to prevent parallel processes from deadl
Next
From: Jim Nasby
Date:
Subject: Re: [patch] Proposal for \crosstabview in psql