Re: Update Unicode data to Unicode 16.0.0

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(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-05 23:34:06
Message-ID: 9826612005cf9d350c716755dcb79bfd2fe53cdd.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthias van de Meent 2025-03-05 23:39:03 Re: Expanding HOT updates for expression and partial indexes
Previous Message Heikki Linnakangas 2025-03-05 23:28:07 Re: Interrupts vs signals