Horton
Menu

Re: PG 19 release notes and authors

Jacob Champion <jacob.champion@enterprisedb.com>

View thread
From: Jacob Champion <jacob.champion@enterprisedb.com>
To: Jelte Fennema-Nio <postgres@jeltef.nl>
Cc: Bruce Momjian <bruce@momjian.us>, "David G. Johnston" <david.g.johnston@gmail.com>, Andrew Dunstan <andrew@dunslane.net>, 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:55:19Z
Lists: pgsql-hackers 
On Mon, Apr 6, 2026 at 8:47 AM Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
> Crazy idea: One option for what we could do going forward is use the
> Author header field of the commit for the actual author, instead of
> having that field always contain the same as the Committer header field.

From a mechanical perspective, that has clear advantages to me
(especially with the de facto GitHub interpretation), but I think it'd
collide with our practice of rewriting commits to maintain project
voice. Maybe people could get used to that change, but I generally
expect the Author in the Git metadata to be the *literal* author of
the commit message.

--Jacob

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