From: Nico Williams <nico@cryptonector.com>
To: Daniel Verite <daniel@manitou-mail.org>
Cc: Jeff Davis <pgsql@j-davis.com>
Cc: Peter Eisentraut <peter@eisentraut.org>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Pre-proposal: unicode normalized text
Date: Thu, 2 Nov 2023 18:17:33 -0500
Message-ID: <ZUQuDS8QN9+rYueh@ubby21> (raw)
In-Reply-To: <f39c5194-14cd-4a5b-822f-382c8b425499@manitou-mail.org>
References: <c5e9dac884332824e0797937518da0b8766c1238.camel@j-davis.com>
<f39c5194-14cd-4a5b-822f-382c8b425499@manitou-mail.org>
On Tue, Oct 17, 2023 at 05:07:40PM +0200, Daniel Verite wrote:
> > * Add a per-database option to enforce only storing assigned unicode
> > code points.
>
> 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.
>
> 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.
Yes, and that's desirable if PG were to normalize text as Jeff proposes,
since then PG wouldn't know how to normalize text containing codepoints
assigned after that. At that point to use those codepoints you'd have
to upgrade PG -- not too unreasonable.
Nico
--
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: nico@cryptonector.com, daniel@manitou-mail.org, pgsql@j-davis.com, peter@eisentraut.org, robertmhaas@gmail.com
Subject: Re: Pre-proposal: unicode normalized text
In-Reply-To: <ZUQuDS8QN9+rYueh@ubby21>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox