Re: Closing commitfest 2013-11 - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Closing commitfest 2013-11
Date
Msg-id 20140121202150.GJ10723@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: Closing commitfest 2013-11  (Vik Fearing <vik.fearing@dalibo.com>)
List pgsql-hackers
Vik Fearing wrote:
> On 01/20/2014 10:31 PM, Tom Lane wrote:
> > I think the idea was that patch authors should take responsibility for
> > pushing their patches forward to 2014-01 if they still wanted them
> > considered.  Quite a few patches already were moved that way, IIRC.
> >
> > Agreed though that we shouldn't let them just rot.
> 
> Does this mean I can resurrect my pg_sleep_until() patch?  I didn't set
> it back to Needs Review after I completely changed my approach based on
> feedback.  I would hate for it to get lost just because I didn't know
> how to use the commitfest app.
> 
> https://commitfest.postgresql.org/action/patch_view?id=1189

No objection here.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Add min and max execute statement time in pg_stat_statement
Next
From: Claudio Freire
Date:
Subject: Re: Re[2]: [HACKERS] Re: [Lsf-pc] Linux kernel impact on PostgreSQL performance (summary v2 2014-1-17)