Horton
Menu

Re: First draft of PG 19 release notes

Bruce Momjian <bruce@momjian.us>

View thread
From: Bruce Momjian <bruce@momjian.us>
To: Michael Banck <mbanck@gmx.net>
Cc: Jacob Champion <jacob.champion@enterprisedb.com>, Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, Heikki Linnakangas <hlinnaka@iki.fi>, PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-16T15:13:51Z
Lists: pgsql-hackers 
On Thu, Apr 16, 2026 at 09:54:57AM +0200, Michael Banck wrote:
> > Well, I am guessing you didn't read this thread fully:
> > 
> > 	https://www.postgresql.org/message-id/flat/adElLtegJxi6Yecv%40momjian.us
> >
> > This was specifically for "Co-authored-by:" == committer, but the text
> > was not clear enough.  However, that doesn't match your usage where a
> > missing "Author" is considered to be the committer.
> 
> I think if the committer omits an "Author" tag, but credits a
> non-committer as "Co-Author", then both the committer and the
> non-committer should be considered authors and credited in the release
> notes.
> 
> What would be the use-case for a sole non-committer "Co-Author" (as
> opposed to just crediting the non-committer as "Author") otherwise be?

I agree with you, and made that case in January of 2025 and in the email
thread URL above.  However, I seemed to annoy people more than help
them, so I am not going to revisit it.  If someone else wants to restart
that thread and get a different consensus, feel free to do so.

My guess is that most (vocal?) committers prefer to have Author and
Co-Author indicate different levels of authorship in the commit text,
rather than have them have different behavior for release note
authorship.

-- 
  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. doc PG 19 relnotes: remove VALIDATE CONSTRAINT lock item

  2. Fix ALTER DOMAIN VALIDATE CONSTRAINT locking

  3. Revert "Enable fast default for domains with non-volatile constraints"

  4. doc PG 19 relnotes: improve awkward or confusing wording

  5. doc PG 19 relnotes: more fixes

  6. doc PG 19 relnotes: various corrections

  7. doc PG 19 relnotes: adjust item to mention pg_replication_slots

  8. doc PG 19 relnotes: remove "Add fake LSN support to hash index"

  9. doc PG 19 relnotes: add two optimizer hooks

  10. doc PG 19 relnotes: remove "Optionally" for CPU optimizations

  11. doc PG 19 relnotes: adjustments/removal of items

  12. doc PG 19 relnotes: add UTF-8 case folding performance item

  13. doc PG 19 relnotes: correct two items

  14. doc PG 19 relnotes: add missing commits and details

  15. doc PG 19 relnotes: fix typo, "date" -> "data"

  16. doc PG 19 relnotes: add author and move items

  17. doc PG 19 relnotes: update author

  18. doc PG 19 relnotes: add free space map all-visible item

  19. doc PG 19 relnotes: remove "Lakshmi N" as author of checksums

  20. doc PG 19 relnotes: fix "now targets"

  21. doc PG 19 relnotes: adjust ShmemRequestStruct item

  22. Improve various new-to-v19 appendStringInfo calls

  23. doc: Fix data_checksums data type

  24. Fix WITHOUT OVERLAPS' interaction with domains.

  25. Online enabling and disabling of data checksums

  26. Doc: split functions-posix-regexp section into multiple subsections.

  27. make immutability tests in to_json and to_jsonb complete

  28. Optimize tuple deformation

  29. pgstattuple: Optimize pgstattuple_approx() with streaming read

  30. Use fake LSNs to improve nbtree dropPin behavior.

  31. Use streaming read for VACUUM cleanup of GIN

  32. Clean up ICU includes.

  33. ICU: use UTF8-optimized case conversion API

  34. Add the MODE option to the WAIT FOR LSN command

  35. Speedup tuple deformation with additional function inlining