Hi Apologies for the intermission in activity, among other "fun" things had a family visitation of the influenza virus, which is becoming fashionable in these parts again.
In an attempt to salvage something from the situation I am having a crack at the older entries marked "Ready for Committer", some of which probably need some sort of action, but it's not always clear (to me at least) what. If there's some sort of consensus for individual items, per previous practice I'll update the individual threads. Date in parenthesis is that of the most recent message on the thread. pg_stat_statements: Track statement entry timestamp (2022-04-08) ---------------------------------------------------------------- - https://commitfest.postgresql.org/40/3048/ - https://www.postgresql.org/message-id/flat/72e80e7b160a6eb189df9ef6f068cce3765d37f8.ca...@moonset.ru Patch is applying but no recent activity. psql - refactor echo code (2022-07-24) -------------------------------------- - https://commitfest.postgresql.org/40/3140/ - https://www.postgresql.org/message-id/flat/alpine.DEB.2.22.394.2105301104400.3020016@pseudo Seems like a small patch which can be applied easily. Add Amcheck option for checking unique constraints in btree indexes (2022-09-28) -------------------------------------------------------------------------------- - https://commitfest.postgresql.org/40/3464/ - https://www.postgresql.org/message-id/flat/calt9zehrn5xam5boga0qnrcmpv52bscek2qnq1hmuzdd301...@mail.gmail.com Seems to be consensus it is actually RfC, but needs a committer to show interest. meson PGXS compatibility (2022-10-13) ------------------------------------- - https://commitfest.postgresql.org/40/3932/ - https://www.postgresql.org/message-id/flat/20221005200710.luvw5evhwf6cl...@awork3.anarazel.de Seems to be RfC. pg_receivewal fail to streams when the partial file to write [...] (2022-10-13) ------------------------------------------------------------------------------- - https://commitfest.postgresql.org/40/3503/ - https://www.postgresql.org/message-id/flat/cahg+qdcvuss6ocomblbv5f4yeglhoct+1x2ylnfg2h_edwu...@mail.gmail.com The author of the latest patch (not the original patch author) indicates this needs further review; should the status be changed? Setting it back to "Needs review" seems the obvious thing to do, but it feels like it would put it back in the pool of possibly unreviewe entries (maybe we need a "Needs futher review" Update relfrozenxmin when truncating temp tables (2022-11-05) ------------------------------------------------------------ - https://commitfest.postgresql.org/40/3358/ - https://www.postgresql.org/message-id/flat/cam-w4hnnbdexixrj0b+_-wvp5nz6of0rlueqfuzfyqblcbe...@mail.gmail.com I'll set this one to "Waiting on Author" based on Tom's latest feedback. Faster pglz compression (2021-11-17) ------------------------------------ - https://commitfest.postgresql.org/40/2897/ - https://www.postgresql.org/message-id/flat/fef3dc5e-4bc4-44e1-8deb-dadc67046...@yandex-team.ru This one, prior to my reminder, has a committer promising to commit but was inactive for over a year. Regards Ian Barwick
