A week ago, I wrote:
> Some numbers: we got 65 patches this time, of which we rejected 4 and
> returned 3 with feedback. 14 patches have already been committed, and
> 13 are waiting on their respective authors. 25 patches need review, and
> 6 are said to be ready for committers.
A week later, numbers have changed but not by much. We now have 66
patches (one patch from the previous commitfest was supposed to be moved
to this one but didn't). Rejected patches are still 4; there are now 7
returned with feedback. 17 are committed, and 10 are waiting on
authors. 21 patches need review.
Most of the remaining Waiting-on-author patches have seen recent
activity, which is why I didn't close them as returned. Authors should
speak up soon -- there is no strict policy but I don't think I'm going
to wait later than this Friday for some final version to be submitted
that can be considered ready for committer. If more work is needed than
simple fixes, authors are encouraged to close such patches as "returned
with feedback" themselves and resubmit during the next commitfest.
Most worrying to me are the large number of patches waiting for a review
-- in some cases they are waiting even for an initial review. Here's a
list:
Server Features
* Timeout framework extension and lock_timeout
* Patch to compute Max LSN of Data Pages
* FOR KEY SHARE foreign keys
* [PoC] Writable Foreign Tables
* Incorrect behaviour when using a GiST index on points
Performance
* Skip checkpoint on promoting from streaming replication
* Decrease GiST bloat when penalties are identical
* Range Types statistics
* Performance Improvement by reducing WAL for Update Operation
* Adjacent in SP-GiST for range-types
* 2d-mapping based GiST for ranges
* Performance Improvement in Buffer Management for Select operation
Security
* Row-Level Security
* Extend argument of OAT_POST_CREATE
System Administration
* New statistics for WAL buffer dirty writes
* Switching timeline over streaming replication
Miscellaneous
* support INSERT INTO...RETURNING with partitioned table using rule
* Reworks for generic ALTER commands
* copy result to psql variables
* FDW for PostgreSQL
* pgbench - custom logging step, estimate of remaining time
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
