Horton

Re: someone else to do the list of acknowledgments

Corey Huinker <corey.huinker@gmail.com>

View thread
From: Corey Huinker <corey.huinker@gmail.com>
To: jian he <jian.universality@gmail.com>
Cc: Aleksander Alekseev <aleksander@timescale.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, Peter Eisentraut <peter@eisentraut.org>
Date: 2025-09-10T15:11:09Z
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.

Attachments

516 contributors this cycle vs 462 last cycle.

When name accents/capitalization differed, I went with the string used in
the previous year.

Some of the names that come from bug reports and doc fixes are just first
names, and the discussion threads shed no light on the full name of the
person.

I have a git log that has been "redacted", which is to say that every name
attribution has been screened out, as well as names of known past
contributors, and various other name-looking things that aren't people (ex.
Microsoft Windows) screened out. Even with all that automation it is still
over 50k lines, so if you want to double check that, make sure you have a
comfy chair.

On Tue, Sep 9, 2025 at 12:07 PM jian he <jian.universality@gmail.com> wrote:

> On Sun, Aug 17, 2025 at 12:40 PM Corey Huinker <corey.huinker@gmail.com>
> wrote:
> >
> > On Sat, Aug 16, 2025 at 11:58 PM jian he <jian.universality@gmail.com>
> wrote:
> >>
> >> hi.
> >> maybe we should start working on this?
> >>
> >> https://www.postgresql.org/developer/roadmap
> >> says 18 will be released in September 2025.
> >
> >
> > I am.
> >
>
> hi.
> Maybe you can share the draft patch so others can review it.
>
> https://www.postgresql.org says:
> "The planned date for the general availability of PostgreSQL 18 is
> September 25, 2025."
>