On Tue, Apr 7, 2015 at 3:35 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
> On 4/7/15 3:33 PM, Tom Lane wrote:
>> I tried to mark the "UPDATE SET (*)" patch as "returned with feedback",
>> but the CF app informed me that if I did that the patch would
>> automatically be moved to the next commitfest. That seems completely
>> stupid. There is no need to reconsider it unless a new version of the
>> patch is forthcoming (which there may or may not ever be, but that's
>> beside the point for now). When and if the author does submit a new
>> patch, that would be the time to include it in the next commitfest, no?
>
> I noticed that as well and have avoided closing some patches because of it.
Several people, including me, have complained about this before. I
hope that Magnus will fix it soon.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
