Re: PG 19 release notes and authors

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: Peter Geoghegan <pg@bowt.ie>, Andrey Borodin <x4mmm@yandex-team.ru>, PostgreSQL-development <pgsql-hackers@lists.postgresql.org>, Joe Conway <mail@joeconway.com>
Date: 2026-04-06T13:40:01Z
Lists: pgsql-hackers
On Sun, Apr  5, 2026 at 04:09:57PM +0200, Álvaro Herrera wrote:
> On 2026-Apr-05, Bruce Momjian wrote:
> > I am not sure PG 19 follows this, but we might want to follow it going
> > forward.
> 
> More and more I am getting the feeling that the commit guidance is
> actually misguided.  The document itself is not very good (I mean, why
> use XML-lookalike to represent a commit message, which is regular
> English prose??); and I don't feel it represents actual consensus.

I agree I am not a fan of the XML, but Joe Conway introduced it and I
didn't object.

> > A larger issue is that since we now have links to the commits in the
> > release notes, there might no longer be a need to list _any_ names next
> > to the release note items.
> 
> I don't understand your motivation for saying things like these.

Uh, I am asking if something is still useful due to recent changes and
can be removed as useless.

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