Horton

Re: Update Unicode data to Unicode 16.0.0

Joe Conway <mail@joeconway.com>

View thread View on postgr.es
From: Joe Conway <mail@joeconway.com>
To: Laurenz Albe <laurenz.albe@cybertec.at>, Jeremy Schneider <schneider@ardentperf.com>, Jeff Davis <pgsql@j-davis.com>
Cc: Nathan Bossart <nathandbossart@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-03-15T14:14:36Z
Lists: pgsql-hackers 
On 3/15/25 03:26, Laurenz Albe wrote:
> On Fri, 2025-03-14 at 23:54 -0700, Jeremy Schneider wrote:
>> On Fri, 07 Mar 2025 13:11:18 -0800
>> It seems the consensus is to update unicode in core... FWIW, I'm still
>> in favor of leaving it alone because ICU is there for when I need
>> up-to-date unicode versions.
> 
> Me too.

+1

>> From my perspective, the whole point of the builtin collation was to
>> one option that avoids these problems that come with updating both ICU
>> and glibc.
> 
> +1

+1

In the long term I think we should figure out how to support newer 
versions of unicode for the builtin, but in my mind that might involve 
the necessity of supporting multiple versions of unicode such that the 
choice remains to remain on the older one.

-- 
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.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