I've closed the following items as Returned with Feedback. These were
all Waiting-on-Author for a long time, with no new versions posted. In
most cases these are still patches that appear to be useful ... but if
they're not kept updated to feedback, they're clutter in the CF system.
patch_id │ author │ name
──────────┼────────────────────┼─────────────────────────────────────────────────────────────────────────────────────────────────────────
1854 │ Aya Iwata │ libpq trace log
2268 │ Ian Barwick │ psql: add tab completion for \df slash command suffixes
1796 │ Chris Travers │ documenting signal handling with readme
2051 │ Karl Pinc │ DOC: Document encode() and decode() base64 encoding
2060 │ takuma hoshiai │ suppress errors thrown by to_reg*()
2082 │ Sandro Mani │ Mingw: Fix import library extension, build actual static libraries
2095 │ Daniel Gustafsson │ pg_upgrade version and path checking
2148 │ Timur Birsh │ vacuumlo: report the number of large objects going to be removed
2223 │ Daniel Migowski │ Adding column "mem_usage" to view pg_prepared_statements
2028 │ Mike Palmiotto │ Flexible partition pruning hook
2108 │ Thomas Munro │ Parallel-aware file_fdw
944 │ Nikhil Sontakke │ Logical decoding of two-phase transactions
1961 │ Petr Jelínek │ Synchronizing slots from primary to standby
2167 │ Peter Eisentraut │ unlogged sequences
2124 │ Matwey V. Kornilov │ Introduce spgist quadtree @<(point,circle) operator
1533 │ Matheus Oliveira │ Add support for ON UPDATE/DELETE actions on ALTER CONSTRAINT
2034 │ Takamichi Osumi │ extension patch of CREATE OR REPLACE TRIGGER
If somebody wants co-authorship for a patch whose author seems
unresponsive, I suggest to ping them about that and run with it if they
don't respond in a reasonable timeframe.
(There were a few others patches Waiting-on-Author, but these didn't
look as stale. I didn't touch anything in the bugfixes section either.)
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services