Closing commitfest 2013-11

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Closing commitfest 2013-11
Date: 2014-01-20 21:24:30
Message-ID: 20140120212430.GD10723@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

* shared memory message queues
This is part of the suite involving dynamic shmem; not sure whether
this is a patch that needs more review, or is it ready for
application, or has it been superceded by later versions in the next
commitfest. Patch authors please chime in.

* 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. (The objection that it will break as soon as we
decide to change the invariant about invalid sockets no longer applies
because it has Asserts to that effect.) Do we really care about
performance during process termination? I'd say this is mildly
interesting if this code is executed for non-authenticated clients.

* Widening application of indices.
Was this re-posted in 2014-01?

* fault tolerant DROP IF EXISTS
I gave a look and it looks good for application. This wasn't
superceded by a future version, correct?

* SSL: better default ciphersuite
I think we should apply this.

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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-01-20 21:24:51 Re: Storing pg_stat_statements query texts externally, pg_stat_statements in core
Previous Message Peter Geoghegan 2014-01-20 21:08:52 Re: Storing pg_stat_statements query texts externally, pg_stat_statements in core