Horton

Re: Update Unicode data to Unicode 16.0.0

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Joe Conway <mail@joeconway.com>, Laurenz Albe <laurenz.albe@cybertec.at>, Jeremy Schneider <schneider@ardentperf.com>, Nathan Bossart <nathandbossart@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-03-19T01:34:50Z
Lists: pgsql-hackers 
On Tue, Mar 18, 2025 at 5:09 PM Jeff Davis <pgsql@j-davis.com> wrote:
> I am not trying to be dismissive of the concerns raised in this thread,
> but I'd like others to understand that what they are asking for is a
> lot of work, and that the builtin collation provider solves 99% of it
> already. All this effort is to solve that last 1%.

I'm not asking you to do the work. It would be great if you did, of
course, but you don't work for me.

But I could not disagree more strongly with the idea that this problem
is 99% solved. That doesn't seem remotely true to me. I'm not sure the
problem is 1% solved.

-- 
Robert Haas
EDB: http://www.enterprisedb.com

Commits

  1. pg_upgrade: Fix memory leak in check_for_unicode_update().

  2. pg_upgrade check for Unicode-dependent relations.

  3. Update Unicode data to Unicode 16.0.0