Message-ID: <dfeff43884f7c3da50e32fc93cb2383255aa2e18.camel@j-davis.com>
Subject: Re: Pre-proposal: unicode normalized text
From: Jeff Davis <pgsql@j-davis.com>
To: Daniel Verite <daniel@manitou-mail.org>
Cc: Peter Eisentraut <peter@eisentraut.org>, Robert Haas
 <robertmhaas@gmail.com>,  pgsql-hackers@postgresql.org
Date: Tue, 17 Oct 2023 09:32:18 -0700
In-Reply-To: <f39c5194-14cd-4a5b-822f-382c8b425499@manitou-mail.org>
References: <f39c5194-14cd-4a5b-822f-382c8b425499@manitou-mail.org>
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/dfeff43884f7c3da50e32fc93cb2383255aa2e18.camel%40j-davis.com>
Precedence: bulk

On Tue, 2023-10-17 at 17:07 +0200, Daniel Verite wrote:
> There's a problem in the fact that the set of assigned code points is
> expanding with every Unicode release, which happens about every year.
>=20
> If we had this option in Postgres 11 released in 2018 it would use
> Unicode 11, and in 2023 this feature would reject thousands of code
> points that have been assigned since then.

That wouldn't be good for everyone, but might it be good for some
users?

We already expose normalization functions. If users are depending on
normalization, and they have unassigned code points in their system,
that will break when we update Unicode. By restricting themselves to
assigned code points, normalization is guaranteed to be forward-
compatible.

Regards,
	Jeff Davis