Re: PG 19 release notes and authors

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Cc: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Bruce Momjian <bruce(at)momjian(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Peter Geoghegan <pg(at)bowt(dot)ie>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PG 19 release notes and authors
Date: 2026-04-06 16:09:41
Message-ID: CA+TgmobSqZZ6NaEw7BvoLUsTAsbTiUPuiZF3=qUfkTBwDzOnOA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 6, 2026 at 11:55 AM Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> 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.

Yes, I think that's right. I would have no problem us allowing pushing
of commits under the actual author's name if the commit is pushed
unchanged, but I rarely push anything unchanged and I think people
would be very quickly become unhappy if I started doing so. In the
rare cases where that would be warranted, the person usually just gets
made a committer anyway.

But really, that's a discussion for another time. The discussion here
is whether we're going to interpret the authorship information in the
existing commits in the way that the committers who created those
commits intended, or whether, as Bruce proposes, we're going to do
something else.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2026-04-06 16:15:47 Re: pgsql: Reduce log level of some logical decoding messages from LOG to D
Previous Message Fujii Masao 2026-04-06 15:57:26 Re: pgsql: Reduce log level of some logical decoding messages from LOG to D