Re: PG 19 release notes and authors
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Bruce Momjian <bruce@momjian.us>, 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-08T11:54:52Z
Lists: pgsql-hackers
On Tue, Apr 7, 2026 at 12:01 AM Robert Haas <robertmhaas@gmail.com> wrote: > > On Mon, Apr 6, 2026 at 1:20 PM Bruce Momjian <bruce@momjian.us> wrote: > > I am confused how this was not clear in the January 2025 discussion and > > why people didn't mention they didn't like it then. I can't quote > > anything from anyone but myself from a private email, so here is some > > text by me to you: > > > > I started using Co-Author as a way to indicate that the Co-Author > > wrote some of the patch, but I modified it enough that I don't want > > to attribute/blame the work entirely on the Co-Author. Are you > > saying when that happens, I should name myself also as a Co-Author? > > I just don't understand what that has to do with the present > situation. The answer to the question you quote here was "yes", but it > doesn't touch on the present question, which is what happens when > there are both 1 or more Author: tags and also 1 or more > Co-authored-by: tags. The unanimous answer from everyone here, except > you, is that all those names should be listed as authors for release > notes purposes. > +1. This is my understanding as well. -- With Regards, Amit Kapila.
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