Horton
Menu

Re: PG 19 release notes and authors

Bruce Momjian <bruce@momjian.us>

View thread
From: Bruce Momjian <bruce@momjian.us>
To: Andrew Dunstan <andrew@dunslane.net>
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-06T15:03:57Z
Lists: pgsql-hackers 
On Mon, Apr  6, 2026 at 10:56:49AM -0400, Andrew Dunstan wrote:
> 
> 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.

So "Co-authored-by:" shows a level of involvement, but doesn't have any
effect on the major release notes.  That works too.

-- 
  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