Horton

someone else to do the list of acknowledgments

Peter Eisentraut <peter@eisentraut.org>

View thread
From: Peter Eisentraut <peter@eisentraut.org>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-04-11T16:25:47Z
Lists: pgsql-hackers

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 list of acknowledgments to release notes

  2. Fix misuse of Relids for storing attribute numbers

  3. meson: build checksums with extra optimization flags.

  4. Fix concurrent update issue with MERGE.

  5. Restrict psql meta-commands in plain-text dumps.

  6. doc: add float as an alias for double precision.

  7. doc: mention unusability of dropped CHECK to verify NOT NULL

  8. Update time zone data files to tzdata release 2025b.

  9. Fix issue with ORDER BY / DISTINCT aggregates and FILTER

  10. Fix guc_malloc calls for consistency and OOM checks

  11. doc: clarify default checksum behavior in non-master branches

  12. Don't ask for bug reports about pthread_is_threaded_np() != 0.

  13. doc: Clarify synchronous_standby_names parameter.

  14. Fix corruption when relation truncation fails.

  15. doc: fix ALTER DOMAIN domain_constraint to spell out options

  16. doc: Add link to listen_addresses as cause of connection failure

  17. doc: Fix INSERT statement syntax for identity columns

  18. Use generateClonedIndexStmt to propagate CREATE INDEX to partitions.

  19. Fix race condition in COMMIT PREPARED causing orphaned 2PC files

  20. vacuumdb: Skip temporary tables in query to build list of relations

  21. Speed up Hash Join by making ExprStates support hashing

  22. Preserve CurrentMemoryContext across Start/CommitTransactionCommand.

I would like for someone else to prepare the list of acknowledgments in
the release notes this year.

I have been preparing the list of acknowledgments in the release notes
(example: [0]) since PostgreSQL 10 (launched from discussions at PGCon
2017 [1]).  I'm looking to hand this off now, so that I'm not hogging
this job forever.

[0]: 
https://www.postgresql.org/docs/17/release-17.html#RELEASE-17-ACKNOWLEDGEMENTS
[1]: 
https://wiki.postgresql.org/wiki/PgCon_2017_Developer_Meeting#Release_notes_scope.2C_and_giving_credit

I'm happy to train the next person and hand them my tips and scripts,
or they can of course define their own processes.

So that prospective candidates know what they are getting into, the
(my) process is approximately:

1. collect names from git logs in semi-automated way
2. sort, organize, fix, and normalize names
3. check manually against git log
4. commit
5. fix up based on public feedback
6. keep updated until release

The whole thing might take about 20 to 30 hours wall-clock time.

I have found it not useful to start this too early, since you'll get a
lot of new names during the beta period.  I have lately usually
started after the August beta release.  (Or you can start early and
keep it updated.  Again, it's your process.)

Anyone can do this, you don't need to be a committer or developer (but
you'll need to be able to produce a well-formed documentation patch).
However, I suggest that because there is a fair amount of work to
normalize, fix, and transliterate names, it would help if you've been
around for a while and have some passing familiarity with the names of
the people around here.  Also, since this list is often cited for
public credit, some care and attention to detail is needed.

So, there is some time to think about this.  Please discuss here if
you're interested or have questions.

(This is presupposing that we still want to do this.  If you have
other ideas for a better list or no list, this is also the time to
discuss this.)