Hackers,
At this point, almost all patches have been assigned to reviewers. If
you submitted a patch and don't get feedback by Saturday, take a look at
who's in the "reviewers" column and send them a query. Since I have no
way to track when patches are assigned to reviewers, I have no idea if
some of them are sitting on their hands.
Some patches have not been assigned to reviewers for various reasons.
The following weren't assigned because they are complex and really need
a high-end hacker or committer to take them on:
libpq events
rmgr hooks and contrib/rmgr_hook
CLUSTER using sort instead of index scan
The following were not assigned because there has already been
discussion on this list debating them being a good idea. These need
consensus on this list before they get assigned to a reviewer:
remove --inputdir and --outputdir from pg_regress
GUC: Case-insensitive units
Allow has_table_privilege(...,'usage') on sequences
I've assigned some reviewers to "WIP" patches with instructions to
report back on their general experience with building, functionality and
spec.
Note that patches need not have only one reviewer! If you have time,
please take on testing some of the more complex patches, especially:
Column-level Permissions
Common Table Expressions
SE-PostgreSQL patches
Also, note that the following patches need performance testing on a
variety of platforms. Everyone should help with this.
GSoC Improved Hash Indexing
posix fadvises
operator restrictivity function for text search
CLUSTER using sort instead of index scan
Thanks for you input, and let's close this commitfest in a week!
--CommitFest "Mom"
