Request a Demo
Home   >   mailing lists

Re: Commitfest PG20-2 is now closed - Mailing list pgsql-hackers

From shihao zhong
Subject Re: Commitfest PG20-2 is now closed
Date
Msg-id CAGRkXqTTQv0SdMWcNBe1H=MTdCMHi51pYsuuEU_CEQL+fE=FiA@mail.gmail.com
Whole thread
In response to Re: Commitfest PG20-2 is now closed  (Jelte Fennema-Nio <postgres@jeltef.nl>)
List pgsql-hackers
Tree view
Hi Alvaro,

> IMO all patches tagged "Bugfix" should be moved forward, regardless of
> thread noise level or whether CI is clean or not.

Agreed. I went through the open Bugfix entries in your three lists.
58 are now in PG20-3, with the tag kept.

7 lost the tag and stayed where they were. Their own threads call them
improvements or hardening, for example psql tab completion and an
added Assert.

5 are closed. 3 were already committed. The other two:

https://commitfest.postgresql.org/patch/5736/
Returned with Feedback. The race only shows up after a code change,
and the thread has been quiet since May 2025.

https://commitfest.postgresql.org/patch/7070/
Rejected. Daniel did not want the change, and the other fixes from
that thread are committed.

If I got one wrong, tell me or just change it back.

For the commitfest app, I opened two PRs.

https://github.com/postgres/pgcommitfest/pull/120
Entries tagged Bugfix are always moved when a CommitFest closes.

https://github.com/postgres/pgcommitfest/pull/121
The "Attach thread" search also finds pgsql-bugs threads, so a fix for
a bug report is easier to register.

Thanks,
Shihao

pgsql-hackers by date:

Previous
From: Henson Choi
Date:
Subject: Re: [PATCH] Add pg_get_table_ddl() to reconstruct CREATE TABLE statements
Next
From: Narayanan Venkateswaran
Date:
Subject: Re: Use instr_time for pg_stat_database block read/write time counters