Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w9kYJ-001i4h-2F for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2026 14:03:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w9kYI-008tt2-0H for pgsql-hackers@arkaria.postgresql.org; Mon, 06 Apr 2026 14:03:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w9kYH-008tss-2E for pgsql-hackers@lists.postgresql.org; Mon, 06 Apr 2026 14:03:42 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1w9kYF-00000000uLC-2Ep8 for pgsql-hackers@lists.postgresql.org; Mon, 06 Apr 2026 14:03:41 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id AD1BC584A92 for ; Mon, 06 Apr 2026 16:03:38 +0200 (CEST) Received: from s980.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id 9D8F95846C5; Mon, 06 Apr 2026 16:03:38 +0200 (CEST) Received: from localhost (unknown [172.22.191.6]) by s980.loopia.se (Postfix) with ESMTP id 9766A22016DC; Mon, 06 Apr 2026 16:03:38 +0200 (CEST) X-Virus-Scanned: amavis at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.2 X-Spam-Level: X-Spam-Status: No, score=-1.2 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1] autolearn=disabled Authentication-Results: s474.loopia.se (amavis); dkim=pass (2048-bit key) header.d=yesql.se Received: from s979.loopia.se ([172.22.191.6]) by localhost (s474.loopia.se [172.22.190.14]) (amavis, port 10024) with UTF8LMTP id NrYJ2Mvw_cvA; Mon, 6 Apr 2026 16:03:37 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.236 Received: from smtpclient.apple (customer-89-255-232-236.stosn.net [89.255.232.236]) (Authenticated sender: daniel@yesql.se) by s979.loopia.se (Postfix) with ESMTPSA id B755510BC4BF; Mon, 06 Apr 2026 16:03:37 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1775484217; bh=5bDFXvRlGHCeQqG1v8XsoYa8Vb69TMNZ6ukGNTNVC/I=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=HxujZ0UAsbjTTQV2yztj+dcDmAenIfnCs3VeFaFQtD2rSj0mR9G0d5Mv/SPodKto6 5LbsacXkFB6RF4k6FFiUBj0QszuaayHFAWeeqNztMz4os+UY1txZiS5Vz67nM2PlQA 6nLiTkFvsRivw0oA2sTOib5Z+tuqGR+XRE5lcM8tFzpY5eLNqoSw3l4w+j/XAJaPbJ /OtYe2kRCLvcmcxGurXNTDAntZt9W3sAz35l7H480l7h8m4T+O4/o3Xn6q++6qnZUi AvXKINxdm/W3tuFKOiiWeZZH7bl6CJDqym8bE5nudgKqbValhtqJn+3sNziXEfYImX Yt//Gc2RJjqtA== Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.2\)) Subject: Re: PG 19 release notes and authors From: Daniel Gustafsson In-Reply-To: Date: Mon, 6 Apr 2026 16:03:27 +0200 Cc: "David G. Johnston" , =?utf-8?Q?=C3=81lvaro_Herrera?= , Peter Geoghegan , Andrey Borodin , PostgreSQL-development Content-Transfer-Encoding: quoted-printable Message-Id: <6CBFA6BE-2CDD-4991-8827-30180794D1B6@yesql.se> References: <202604051405.sxedzcgzky3n@alvherre.pgsql> To: Bruce Momjian X-Mailer: Apple Mail (2.3776.700.51.11.2) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 6 Apr 2026, at 15:57, Bruce Momjian wrote: > Wow, I never thought that was a valid pattern, but I see a few PG 19 > commit messages using that, e.g.: >=20 > Author: Peter Eisentraut > 2025-08-12 [5f19d13df] libpq: Set LDAP protocol version 3 >=20 > libpq: Set LDAP protocol version 3 >=20 > Some LDAP servers reject the default version 2 protocol. So set > version 3 before starting the connection. This matches how the > backend LDAP code has worked all along. >=20 > Co-authored-by: Andrew Jackson > Reviewed-by: Pavel Seleznev > Discussion: = https://www.postgresql.org/message-id/flat/CAKK5BkHixcivSCA9pfd_eUp7wkLRhv= Q6OtGLAYrWC%3Dk7E76LDQ%40mail.gmail.com >=20 > Is that what people are using? A missing Author, and co-authors means > the committer is the author? Right? Shouldn't we document this? = That > does give a unique use for Co-authored-by. My online checksums commit use a similar pattern, which is how I had interpreted our use of it. It lists myself and Magnus as authors with = Tomas Vondra as co-auhor since he provided substantial changes to the patch. A missing Author tag should IMO always mean that the committer is the = author. >> do think we have enough structured data that if we felt our = attribution efforts >> were insufficient there are more things we could do. I=E2=80=99m not = sure this is the >> most valuable way to expose this data but it=E2=80=99s a way, we = likely don=E2=80=99t do enough >> promotion even with it, and it seems low maintenance. But maybe = there is a >> cost/benefit discussion to be had here. >=20 > I guess that is my question. I don't think the author names have the > same practical value now that we have commit links, but if people = think > it still has _sufficient_ value, we should keep it --- that was my > question. I know from talking to several contributors that seeing their name next = to the feature in the release notes is a huge motivator. -- Daniel Gustafsson