Re: Update Unicode data to Unicode 16.0.0

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: 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-06 02:43:57
Message-ID: Z8kL7fSNXVgMTG9m@nathan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 05, 2025 at 03:34:06PM -0800, Jeff Davis wrote:
> On Wed, 2025-03-05 at 14:33 -0600, Nathan Bossart wrote:
>> +               report_status(PG_WARNING, "warning");
>> +               pg_log(PG_WARNING, "Your installation contains
>> relations that may be affected by a new version of Unicode.\n"
>> +                          "A list of potentially-affected relations
>> is in the file:\n"
>> +                          "    %s", report.path);
>>
>> This may have been discussed upthread, but is a warning enough?  That
>> seems
>> like something that could very easily be missed.
>
> There can be false positives, because even if such an expression index
> exists, it's often not an actual problem. Do we want to stop an upgrade
> from happening in that case? I doubt it, but if so, we'd need some kind
> of option to bypass it.

I see. Do we provide any suggested next steps for users to assess the
potentially-affected relations?

--
nathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2025-03-06 02:49:15 Re: what's going on with lapwing?
Previous Message Nathan Bossart 2025-03-06 02:34:37 Re: optimize file transfer in pg_upgrade