Re: Built-in CTYPE provider

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Daniel Verite <daniel(at)manitou-mail(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jeremy Schneider <schneider(at)ardentperf(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Built-in CTYPE provider
Date: 2024-07-09 01:17:52
Message-ID: 1260021.1720487872@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Noah Misch <noah(at)leadboat(dot)com> writes:
> It sounds like you're very comfortable with $SUBJECT proceeding in its current
> form. Is that right?

I don't have an opinion on whether the overall feature design
is well-chosen. But the mere fact that Unicode updates will
from time to time change the behavior (presumably only in edge
cases or for previously-unassigned code points) doesn't strike
me as a big enough problem to justify saying these functions
can't be marked immutable anymore. Especially since we have been
faced with that problem all along anyway; we just didn't have a way
to track or quantify it before, because locale changes happened
outside code we control.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andy Fan 2024-07-09 01:18:11 Re: Parallel CREATE INDEX for GIN indexes
Previous Message Noah Misch 2024-07-09 01:05:45 Re: Built-in CTYPE provider