Re: Built-in CTYPE provider - Mailing list pgsql-hackers

From Jeremy Schneider
Subject Re: Built-in CTYPE provider
Date
Msg-id CA+fnDAa+1ERVFYjSStnR9WTQ6Z1jBcKLW6qG4SU4RYYdqw_PEw@mail.gmail.com
Whole thread Raw
In response to Re: Built-in CTYPE provider  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-hackers
On Tue, Jul 9, 2024 at 4:00 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:

My personal exprience is that very few users are aware of or care about
the strict accuracy of the collation sort order and other locale aspects.
But they care a lot about index corruption.

So I'd argue that we should not have any breaking changes at all, even in
cases where the provider is clearly wrong.


FWIW, using external ICU libraries is a nice solution for users who need strict and up-to-date Unicode support.

Cell phones do often get support for new code points before databases. So databases can end up storing characters before they are aware of the meaning. (Slide 27 in the pgconf.dev talk illustrates a recent timeline of Unicode & phone updates.)

-Jeremy

pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: Document DateStyle effect on jsonpath string()
Next
From: Junwang Zhao
Date:
Subject: Re: jsonpath: Inconsistency of timestamp_tz() Output