Re: PostgreSQL 18 GA press release draft

Nico Williams <nico@cryptonector.com>

From: Nico Williams <nico@cryptonector.com>

To: Jeff Davis <pgsql@j-davis.com>

Cc: "Jonathan S. Katz" <jkatz@postgresql.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-09-12T18:21:06Z

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 →

Add modern SHA-2 based password hashes to pgcrypto.
- 749a9e20c979 18.0 cited
Convert 'x IN (VALUES ...)' to 'x = ANY ...' then appropriate
- c0962a113d1f 18.0 cited
Allow usage of match_orclause_to_indexcol() for joins
- 627d63419e22 18.0 cited

On Fri, Sep 12, 2025 at 10:11:59AM -0700, Jeff Davis wrote:
> The name PG_UNICODE_FAST is meant to convey that it provides full
> unicode semantics for case mapping and pattern matching, while also
> being fast because it uses memcmp for comparisons. While the name
> PG_C_UTF8 is meant to convey that it's closer to what users of the libc
> "C.UTF-8" locale might expect.

How does one do form-insensitive comparisons?

Nico
--