Re: Update Unicode data to Unicode 16.0.0

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Jeremy Schneider <schneider(at)ardentperf(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Update Unicode data to Unicode 16.0.0
Date: 2025-03-15 07:26:11
Message-ID: a7238bdd651bb150eff0de421472ba79adcf3e06.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

> 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

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2025-03-15 08:40:39 Re: Enhancing Memory Context Statistics Reporting
Previous Message Jeremy Schneider 2025-03-15 06:54:41 Re: Update Unicode data to Unicode 16.0.0