Re: Built-in CTYPE provider

Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> On Thu, 2024-07-18 at 07:00 -0700, Noah Misch wrote:
>> Maybe someone will change
>> something in v18 so it's not like that, but don't count on it.

> That's backwards. If nothing happens in v18, then there will be no
> breaking Unicode change. It takes an active step by a committer to
> update Unicode.

This whole discussion seems quite bizarre to me. In the first
place, it is certain that Unicode will continue to evolve, and
I can't believe that we'd just freeze pg_c_utf8 on the current
definition forever. Whether the first change happens in v18
or years later doesn't seem like a particularly critical point.

In the second place, I cannot understand why pg_c_utf8 is being
held to a mutability standard that we have never applied to any
other locale-related functionality --- and indeed could not do
so, since in most cases that functionality has been buried in
libraries we don't control. It seems to me to be already a
great step forward that with pg_c_utf8, at least we can guarantee
that the behavior won't change without us knowing about it.
Noah's desire to revert the feature makes the mutability situation
strictly worse, because people will have to continue to rely on
OS-provided functionality that can change at any time.

regards, tom lane