CommitFest Status Summary - 2009-07-25 - Mailing list pgsql-hackers
From | Robert Haas |
---|---|
Subject | CommitFest Status Summary - 2009-07-25 |
Date | |
Msg-id | 603c8f070907251751s3d67e18dyeb5b5957c98aa15f@mail.gmail.com Whole thread Raw |
Responses |
Re: CommitFest Status Summary - 2009-07-25
|
List | pgsql-hackers |
All, A few hours ago I assigned a reviewer to the last patch for this CommitFest which still lacked one, with the exception of Heikki's index-only quals patch, which I'm not sure can be reviewed at this point because it depends on the indexam API changes patch, which is still up in the air. One thing I have belatedly realized about this CommitFest is that we (or at least, I) did not think about asking the committers about their schedules, and it turns out that three of them - Heikki, Michael Meskes, Joe Conway - are away at the moment. About 25% of the remaining patches are waiting for one of those three people to take the next step (as either patch author, or reviewer, or committer). That's not exactly a catastrophe considering that we have informally decided that a CommitFest is about a month long, and we're only 10 days into it, but may mean that there's not much left for non-committers to do well before all of the patches are actually dealt with. I've attached below a summary of which patches are waiting on which people, to the best of my ability to determine such things. It's basically the same information that's on commitfest.postgresql.org, but broken up differently and annotated with notes here and there. There are a couple of patches that are ostensibly waiting on reviewer activity that may really be ready for committer; the others are reviews that aren't finished, and we may want to think about adding additional reviewers to help move things along. Also, there are a few patches that are waiting on author which are nearly done, and it may make sense for someone other than the patch author to pick them up and finish them so that we can move forward with them. Any thoughts/ideas/etc. welcome. ...Robert Specific Committers (13) - generic explain options v3 (needs further review by Tom Lane) - Indexam API changes (Heikki Linnakangas as patch author) - Index-only quals (Heikki Linnakangas as patch author) - Determine cient_encoding from client locale (Heikki Linnakangas as patch author) - plpythonu datatype conversion improvements (Peter Eisentraut as committer) - dependencies for generated header files (Peter Eisentraut as reviewer) - Fix memory leak in win32 security functions (Magnus Hagander as patch author and presumed committer) - ECPG dynamic cursor, SQLDA support (Michael Meskes as reviewer) - ECPG support for string pseudo-type v2 (Michael Meskes as reviewer) - async notifications for dblink (Joe Conway as reviewer) - query cancel issues in dblink (Joe Conway as reviewer) - has_sequence_privilege() function (Joe Conway as reviewer) - Polygons (Teodor Sigaev as committer) Unspecified Committer (4) - GRANT ON ALL IN schema - Provide support for multiplexing SIGUSR1 signal - Deferrable unique constraints - DefaultACLs Reviewer (10) - ALTER TABLE ... ALTER COLUMN ... SET DISTINCT - Revise parallel pg_restore's scheduling heuristic - Merge append - Support for EEEE in to_char() (may be ready for committer) - multi-threaded pgbench (may be ready for committer) - Improvements for dict_xsyn extended synonym dictionary - new bytea hex output format - return query and dropped columns (perhaps this should be marked ready for committer?) - Prefix support for synonym dictionary (just assigned) - Filtering dictionary support and unaccent dictionary (just assigned) Author (8) - Named and mixed notation for PL - \dL for languages - WIP: TODO Item 'Add prompt escape to display the client and server versions' - hstore enhancements - Lock wait statistics (Tom doesn't like it, may be doomed) - Parser's hook based on FuncCall (seems to need major expansion, may be too much for this CF) - autogenerating headers & bki stuff (Tom doesn't like it, may be doomed) - better support for win64 via intptr_t (seems to need major reworking, may be too much for this CF) Limbo (2) - machine-readable explain output v2 (can't update this patch until issues with generic explain options v3 are resolved) - report key values in duplicate-key errors (not really sure whose court the ball is in at this point)
pgsql-hackers by date: