Re: PG 19 release notes and authors
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Bruce Momjian <bruce@momjian.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-06T17:05:18Z
Lists: pgsql-hackers
On Mon, Apr 6, 2026 at 12:41 PM Bruce Momjian <bruce@momjian.us> wrote: > Uh, the original wiki text is from a discussion on > pgsql-private-committers@lists.postgresql.org with subject "determining > the primary author of a commit" that happened around November 2024 to > March 2025. Unfortunatly there is no public archive of that > discussion. Sure, but many committers who were part of that discussion have commented on this thread, and all of them except for you seem to agree on what should happen here, as do all of the people who have commented who were not party to that discussion. If you had started out this conversation by saying "when there are both Author and Co-authored-by tags, how am I supposed to credit that in the release notes?" and accepted the answer you got back, I don't think anybody would be annoyed. But now you're getting frustrated responses from a bunch of people because you keep insisting that it must be everyone else who is mistaken: you keep suggesting that I (and all the other committers who have commented) misunderstood the earlier thread and the rules for commit messages, rather than concluding that you might have been the one who misunderstood. It is fair to say that you need to know what the rules are, but I really don't understand how it could be any more clear at this point what people expect to have happen. -- Robert Haas EDB: http://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