Re: Update Unicode data to Unicode 16.0.0

Jeff Davis <pgsql@j-davis.com>

From: Jeff Davis <pgsql@j-davis.com>
To: Jeremy Schneider <schneider@ardentperf.com>
Cc: Peter Eisentraut <peter@eisentraut.org>, Laurenz Albe <laurenz.albe@cybertec.at>, Joe Conway <mail@joeconway.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-01-21T02:45:14Z
Lists: pgsql-hackers
On Mon, 2025-01-20 at 17:06 -0800, Jeremy Schneider wrote:
> FWIW, after adding ICU support I personally don't think there's a
> pressing need to continue updating the tables anymore.

I agree that it's not a pressing concern.

> If Postgres does go the path of multiple tables, does the community
> want to accumulate a new set of tables every year? That could add up
> quickly. Maybe we don't add new tables every year, but follow the
> examples of Oracle and DB2 in accumulating them on a less frequent
> basis?

Yeah, it would probably be every-other-release or something. By the
time we built up enough versions for someone to worry about, hopefully
we'd have some better systems in place to track versions and migrate
forward.

Regards,
	Jeff Davis




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