Re: 回复:someone else to do the list of acknowledgments

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: 李海洋(陌痕) <mohen.lhy@alibaba-inc.com>
Cc: "Corey Huinker" <corey.huinker@gmail.com>, "jian he" <jian.universality@gmail.com>, "Aleksander Alekseev" <aleksander@timescale.com>, "pgsql-hackers" <pgsql-hackers@postgresql.org>, "Peter Eisentraut" <peter@eisentraut.org>
Date: 2025-09-11T06:50:17Z
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.

"=?UTF-8?B?5p2O5rW35rSLKOmZjOeXlSk=?=" <mohen.lhy@alibaba-inc.com> writes:
> Apologies for jumping in with an unrelated question — I just happened
> to see this email. For the acknowledgment list, is the cutoff point the date of the
>  PostgreSQL 18 official release (September 25, 2025), or does it refer to an earlier date?

I'm not sure that we have an official policy on that point.
My own take on it would be "are you mentioned in the commit
log leading up to 18.0?" (or some slightly-earlier point where
the release notes are finalized).  It's not really about dates
but about contributions to that branch; otherwise we might be
falsely crediting people who worked on 19.x but not 18.x.

Also ... in the big scheme of things, we are way more interested
in crediting ongoing contributors than single events.  So if
you're there in the 19, 20, etc release notes but not 18.0,
I think you should be okay with that.  Everybody started sometime.

			regards, tom lane