| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Jeremy Schneider <schneider(at)ardentperf(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, 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-17 17:31:44 |
| Message-ID: | 58f37f7f1bfab5d6338e462c35957b07019db155.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-03-17 17:33:18 | dead code in pg_upgrade |
| Previous Message | Masahiko Sawada | 2025-03-17 17:27:08 | Re: Restrict copying of invalidated replication slots |