Re: Update Unicode data to Unicode 16.0.0 - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Update Unicode data to Unicode 16.0.0
Date
Msg-id 1e1f69da35419af44bdd85d3e94cd44fa0d38ca5.camel@j-davis.com
Whole thread Raw
In response to Re: Update Unicode data to Unicode 16.0.0  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Update Unicode data to Unicode 16.0.0
List pgsql-hackers
On Wed, 2025-03-19 at 14:33 -0400, Robert Haas wrote:

> I strongly believe users want to control what happens, not have
> the system try to fix it for them automatically without their
> knowledge.

Do you have a sketch of what the ideal Unicode version management
experience might look like? Very high level, like "this is what happens
by default during an upgrade" and "this is how a user discovers that
that they might want to update Uniocde", etc.

What ways can/should we nudge users to update more quickly, if at all,
so that they are less likely to have problems with newly-assigned code
points?

And, if possible, how we might extend this user experience to libc or
ICU updates?

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Marcos Pegoraro
Date:
Subject: Re: Doc: Fixup misplaced filelist.sgml entities and add some commentary
Next
From: Thomas Munro
Date:
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER