Horton
Menu

Re: PG 19 release notes and authors

David G. Johnston <david.g.johnston@gmail.com>

View thread
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.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-06T14:42:52Z
Lists: pgsql-hackers 
On Monday, April 6, 2026, Bruce Momjian <bruce@momjian.us> wrote:

>
> I think having "Co-authored-by:" mean one thing when "Author" appears
> and a different thing when "Author" is missing is too confusing.
>

The community hasn’t recognized intermediate contributions between
authorship and reviewer.  Co-Author has always been available for technical
reasons but doesn’t actually convey less status than Author even if some
people intended it to be used that way.  I don’t think we should change
that.  Stating it more clearly seems warranted.

Co-authored never means any thing different than “one of the authors”.
It’s committed-by whose meaning changes in the presence/absence of author.
I likewise don’t see changing that.  For future users of this information,
having a silent boundary at which the meaning/usage of labels changes is
very annoying.

David J.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add tests for lock statistics, take two

  2. Introduce a new mechanism for registering shared memory areas