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 58f37f7f1bfab5d6338e462c35957b07019db155.camel@j-davis.com
Whole thread Raw
In response to Re: Update Unicode data to Unicode 16.0.0  (Jeremy Schneider <schneider@ardentperf.com>)
Responses Re: Update Unicode data to Unicode 16.0.0
List pgsql-hackers
On Sat, 2025-03-15 at 18:23 -0700, Jeremy Schneider wrote:
> Is the simple answer that functions & clauses related to both time
> zones and character semantics should just all be considered STABLE
> instead of IMMUTABLE?

That was discussed a few times, but:

(a) That doesn't exactly solve the problem, because people still need
indexes on LOWER() or CASEFOLD(); and

(b) If we change IMMUTABLE to mean "returns the same results on every
platform for all time", that would be too strict for many purposes,
like the planner doing constant folding.

I have been thinking about ways we can express the right dependencies,
and I may be making some proposals along those lines.

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Restrict copying of invalidated replication slots
Next
From: Nathan Bossart
Date:
Subject: dead code in pg_upgrade