Horton

Re: Update Unicode data to Unicode 16.0.0

Laurenz Albe <laurenz.albe@cybertec.at>

View thread View on postgr.es
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Robert Haas <robertmhaas@gmail.com>, Jeff Davis <pgsql@j-davis.com>
Cc: Peter Eisentraut <peter@eisentraut.org>, Jeremy Schneider <schneider@ardentperf.com>, Nathan Bossart <nathandbossart@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-03-21T23:45:08Z
Lists: pgsql-hackers 
On Fri, 2025-03-21 at 14:54 -0400, Robert Haas wrote:
> And nobody has refuted the argument that refusing to
> update the Unicode tables will cause other problems (such as not
> knowing what to do with new code points that are added in the other
> places where those tables are used).

The argument is irrefutable.
I can only utter my (unproven) conviction that the complaints about
some outlandish character being converted to upper case in the wrong
way won't be as loud as the complaints about a corrupted index.

But perhaps both occurrences would be rare enough that there is
little point in arguing at all.

> People who aren't doing the work
> to improve the infrastructure don't get to hold the longstanding
> process hostage.

Actually, I am arguing for *not* doing the work...

Yours,
Laurenz Albe

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