Here's an attempt on my part to summarize the status of the remaining patches.
* SE-PostgreSQL. Generally positive feedback from Heikki. New
version expected Monday 3/9, with changes to walker.c as requested by
Heikki. Rest of patch reviewable in the meantime.
http://archives.postgresql.org/pgsql-hackers/2009-03/msg00192.php
* GIN fast insert. Tom Lane committed some planner changes that make
it possible for an AM to not support index scans, and posted the
remaining patch. No one other than me has spoken in favor of retaing
support for index scans, so maybe Teodor should just apply the rest of
this (perhaps with the minor wordsmithing I suggested in the second
message linked below, or something similar). Or if not, then we
should decide that this will wait for 8.5 - it's time to fish or cut
bait.
http://archives.postgresql.org/pgsql-hackers/2009-03/msg00220.php
http://archives.postgresql.org/pgsql-hackers/2009-03/msg00224.php
* B-Tree emulation for GIN. Teodor posted a new version of this patch
and is awaiting a response to a few questions he had.
http://archives.postgresql.org/pgsql-hackers/2009-03/msg00198.php
* Improve Performance of Multi-Batch Hash Join for Skewed Data Sets.
Tom Lane reviewed this patch, and Ramon Lawrence responded, but it's
not clear to me where we go from here.
http://archives.postgresql.org/pgsql-hackers/2009-03/msg00273.php
* Proposal of PITR performance improvement. Fujii Masao posted an
updated version of this patch. I believe it has yet to be reviewed by
a committer.
http://archives.postgresql.org/pgsql-hackers/2009-03/msg00064.php
* Reducing some DDL Locks to ShareLock. A substantial part of this
was committed, and there hasn't been a new version of this patch in
three months, so I think it should be bounced at this point. But I
don't want to do that myself unless someone at least makes some kind
of noise of agreement. Can I get a +1, or two?
...Robert
