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

From Tom Lane
Subject Re: Closing commitfest 2013-11
Date
Msg-id 3803.1390253508@sss.pgh.pa.us
Whole thread Raw
In response to Closing commitfest 2013-11  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Closing commitfest 2013-11
Re: Closing commitfest 2013-11
List pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> With apologies to our beloved commitfest-mace-wielding CFM, commitfest
> 2013-11 intentionally still contains a few open patches.  I think that
> CF is largely being ignored by most people now that we have CF 2014-01
> in progress.  If we don't want to do anything about these patches in the
> immediate future, I propose we move them to CF 2014-01.

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.


> * shared memory message queues

Isn't this committed?  There's something by that name breaking the
buildfarm ;-)

> * Shave a few instructions from child-process startup sequence
>   Discussion stalled without a conclusion; opinions diverge on whether
>   this is a useful patch to have.  My personal inclination is to drop
>   this patch because it seems pointless, but if someone feels otherwise
>   I won't object.

I was one of the people objecting to it, so +1 for dropping.
> * Widening application of indices.
>   Was this re-posted in 2014-01?

Yes, there's a newer version already in 2014-01.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Storing pg_stat_statements query texts externally, pg_stat_statements in core
Next
From: Oskari Saarenmaa
Date:
Subject: Re: [PATCH] pg_basebackup: progress report max once per second