2014-10 CommitFest

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: 2014-10 CommitFest
Date: 2014-10-16 18:27:42
Message-ID: 1413484062.4025.YahooMailNeo@web122304.mail.ne1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I just tripped over that CommitFest mace that went missing after
Heikki put it down from the last CF. Unless someone else wants to
pick it up, I'll manage this one.

Just to get the ball rolling, I note that 19 patches were moved to
this CF from the last one. These are in the following states:

Committed
pg_dump refactor to remove global variables

Ready for Committer
Using Levenshtein distance to HINT a candidate column name
Custom Plan API
pgcrypto: support PGP signatures
pg_basebackup vs. Windows and tablespaces
(Extend base backup to include symlink file used to restore symlinks)
run xmllint during build

Waiting on Author
Function returning the timestamp of last transaction
Flush buffers belonging to unlogged tables

Needs Review - with reviewer(s)
Selectivity estimation for inet operators
Fix local_preload_libraries to work as expected.
KNN-GiST with recheck
Abbreviated keys
(Was: Sort support for text with strxfrm() poor man's keys)
Scaling shared buffer eviction
Foreign table inheritance
Grouping Sets
Allow parallel cores to be used by vacuumdb
storage parameter specifying the maximum size of GIN pending list
Stating the significance of Lehman & Yao in the nbtree README

Needs Review - without reviewer
Fix xpath() to return namespace definitions
(fixes the issue with nested or repeated xpath())

So it would be particularly nice if someone could sign up for that
last one.

If nobody else jumps in just itching to manage this CF, I'll follow
up tomorrow with more details. Meanwhile, please sign up to review
a patch!

Since there was no previous warning, I'll allow a grace day for the
cut-off on submissions for this CF; if it isn't registered in the
web application 24 hours after this email, I will move it to the
next CF. So look for those patches that "fell through the cracks"
without getting registered, and post the ones you've got.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2014-10-16 18:32:05 Re: UPSERT wiki page, and SQL MERGE syntax
Previous Message Peter Geoghegan 2014-10-16 18:01:57 Re: UPSERT wiki page, and SQL MERGE syntax