Message-ID: <d1d5640e98e831c3df38f71a4b5ed09f517e668d.camel@j-davis.com>
Subject: Re: First draft of PG 17 release notes
From: Jeff Davis <pgsql@j-davis.com>
To: Bruce Momjian <bruce@momjian.us>, PostgreSQL-development
	 <pgsql-hackers@postgresql.org>
Date: Fri, 17 May 2024 13:30:03 -0700
In-Reply-To: <ZjxLJpnH4VMkOMmi@momjian.us>
References: <ZjxLJpnH4VMkOMmi@momjian.us>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.44.4-0ubuntu2 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/d1d5640e98e831c3df38f71a4b5ed09f517e668d.camel%40j-davis.com>
Precedence: bulk

On Thu, 2024-05-09 at 00:03 -0400, Bruce Momjian wrote:
> I have committed the first draft of the PG 17 release notes;=C2=A0 you ca=
n
> see the results here:
>=20
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0https://momjian.us/pgsql_=
docs/release-17.html

For this item:

    Create a "builtin" collation provider similar to libc's C
    locale (Jeff Davis)

    It uses a "C" locale which is identical but independent of
    libc, but it allows the use of non-"C" collations like "en_US"
    and "C.UTF-8" with the "C" locale, which libc does not. MORE?=20

I suggest something more like:

    New, platform-independent "builtin" collation
    provider. (Jeff Davis)

    Currently, it offers the "C" and "C.UTF-8" locales. The
    "C.UTF-8" locale combines stable and fast code point order
    collation with Unicode character semantics.

Regards,
	Jeff Davis