Horton
Menu

Re: PG 19 release notes and authors

Bruce Momjian <bruce@momjian.us>

View thread
From: Bruce Momjian <bruce@momjian.us>
To: John Naylor <johncnaylorls@gmail.com>
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:55:22Z
Lists: pgsql-hackers 
On Mon, Apr  6, 2026 at 09:47:32PM +0700, John Naylor wrote:
> > I think having "Co-authored-by:" mean one thing when "Author" appears
> > and a different thing when "Author" is missing is too confusing.
> 
> My take is that the co-author tag has backfired and made things less
> clear. If we are using it inconsistently, then it doesn't convey any
> useful information. I'd actually rather just use "Author" exclusively
> and if there is some further detail that needs to be conveyed, it can
> be in the message body.

The original intent as I understood it was for "Co-authored-by:" to be
lesser authors, typically the committer, but as you said, we haven't
done that consistently in the past.  Do we want to do it consistently
going forward or just not use "Co-authored-by:"?

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.

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