Re: PG 19 release notes and authors
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Bruce Momjian <bruce@momjian.us>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>, Álvaro Herrera <alvherre@kurilemu.de>, Peter Geoghegan <pg@bowt.ie>, Andrey Borodin <x4mmm@yandex-team.ru>, PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-06T14:56:49Z
Lists: pgsql-hackers
On 2026-04-06 Mo 10:29 AM, Bruce Momjian wrote: > I think having "Co-authored-by:" mean one thing when "Author" appears > and a different thing when "Author" is missing is too confusing. > Possibly. I think we're tying ourselves up in knots needlessly here, though. To me, without having to interpret the exact meaning by consulting a wiki, Co-authored-by signifies that the person made a significant contribution, but not as much as the Author(s). These things shouldn't be technical terms of art. Personally, I'm in favor of being fairly liberal about giving release note credits. cheers andrew -- Andrew Dunstan EDB:https://www.enterprisedb.com
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add tests for lock statistics, take two
- 557a9f1e3e62 19 (unreleased) cited
-
Introduce a new mechanism for registering shared memory areas
- 283e823f9dcb 19 (unreleased) cited