Re: 回复:someone else to do the list of acknowledgments
Tom Lane <tgl@sss.pgh.pa.us>
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add list of acknowledgments to release notes
- 142885d38053 18.0 landed
-
Fix misuse of Relids for storing attribute numbers
- 2d756ebbe857 19 (unreleased) cited
-
meson: build checksums with extra optimization flags.
- a7024398b80a 18.0 cited
-
Fix concurrent update issue with MERGE.
- c70b6db34ffe 18.0 cited
-
Restrict psql meta-commands in plain-text dumps.
- 67a2fbb8f9e9 18.0 cited
-
doc: add float as an alias for double precision.
- 31c09ef45636 18.0 cited
-
doc: mention unusability of dropped CHECK to verify NOT NULL
- 7b1053a57749 18.0 cited
-
Update time zone data files to tzdata release 2025b.
- 368c3fbf9da9 18.0 cited
-
Fix issue with ORDER BY / DISTINCT aggregates and FILTER
- d47f922246b5 18.0 cited
-
Fix guc_malloc calls for consistency and OOM checks
- 058b5152f02e 18.0 cited
-
doc: clarify default checksum behavior in non-master branches
- 901a1cf8b4a2 18.0 cited
-
Don't ask for bug reports about pthread_is_threaded_np() != 0.
- 4f15759bdcdd 18.0 cited
-
doc: Clarify synchronous_standby_names parameter.
- 6313a76b355e 18.0 cited
-
Fix corruption when relation truncation fails.
- 38c579b08988 18.0 cited
-
doc: fix ALTER DOMAIN domain_constraint to spell out options
- 4200fea80e79 18.0 cited
-
doc: Add link to listen_addresses as cause of connection failure
- 1eb5564230a3 18.0 cited
-
doc: Fix INSERT statement syntax for identity columns
- 17b4aa77c3a1 18.0 cited
-
Use generateClonedIndexStmt to propagate CREATE INDEX to partitions.
- 68dfecbef210 18.0 cited
-
Fix race condition in COMMIT PREPARED causing orphaned 2PC files
- cf4401fe6cf5 18.0 cited
-
vacuumdb: Skip temporary tables in query to build list of relations
- 1ab67c9dfaad 18.0 cited
-
Speed up Hash Join by making ExprStates support hashing
- adf97c156238 18.0 cited
-
Preserve CurrentMemoryContext across Start/CommitTransactionCommand.
- 1afe31f03cd2 18.0 cited
"=?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