Hi.
There are 92 outstanding patches in this CommitFest, and 63 of them do
not have any reviewer. Those are very large numbers, so I hope everyone
will pitch in to keep things moving along.
There's quite a variety of patches available for review this time, and
any level of feedback about them is useful, from "no longer applies to
HEAD" or "doesn't build" to more detailed reviews.
If you don't have the time to do a full review, or are getting bogged
down, post whatever you do have (the same amount of fame and fortune
will still be yours!).
If you're wondering where to start, here are some suggestions, picked
almost at random:
Using Levenshtein distance to HINT a candidate column name
http://archives.postgresql.org/message-id/cam3swzs9-xr2ud_j9yrkdctt6xxy16h1eugtswmlu6or4ct...@mail.gmail.com
Better partial index-only scans
http://archives.postgresql.org/message-id/CABz-M-GrkvrMc9ni5S0mX53rtZg3=szneyru_a8rigq2b3m...@mail.gmail.com
Use unique index for longer pathkeys
http://archives.postgresql.org/message-id/[email protected]
SQL access to database attributes
http://archives.postgresql.org/message-id/[email protected]
pg_resetxlog option to change system identifier
http://archives.postgresql.org/message-id/[email protected]
pg_xlogdump --stats
http://archives.postgresql.org/message-id/[email protected]
tab completion for set search_path TO
http://archives.postgresql.org/message-id/CAMkU=1xJzK0h7=0_sOLLKGaf7zSwp_YzcKwuG41Ns+_Qcn+t=g...@mail.gmail.com
idle_in_transaction_timeout
http://archives.postgresql.org/message-id/[email protected]
I'll post a periodic summary to the list, and will send out reminders by
private mail as usual.
Please feel free to contact me with questions.
-- Abhijit
P.S. If you tag your reviews with [REVIEW] in the Subject, it'll be
easier to keep track of them.
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
