Are datcollate/datctype always libc even under --with-icu ?

Started by Chapman Flackabout 4 years ago2 messages
#1Chapman Flack
chap@anastigmatix.net

... ok, I see that the answer is yes, according to the commit comment
for eccfef8:

Currently, ICU-provided collations can only be explicitly named
collations. The global database locales are still always libc-provided.

I got there the long way, by first wondering how to tell whether a
datcollate or datctype string was intended for libc or ICU, and then
reading pg_perm_setlocale, and then combing through the docs at
CREATE DATABASE and createdb and initdb and Collation Support and
pg_database and the release notes for 10, sure that I would find
the answer staring at me in one of those places once I knew I was asking.

Next question: the "currently" in that comment suggests that could change,
but is there any present intention to change it, or is this likely to just
be the way it is for the foreseeable future?

Regards,
-Chap

#2Daniel Verite
daniel@manitou-mail.org
In reply to: Chapman Flack (#1)
Re: Are datcollate/datctype always libc even under --with-icu ?

Chapman Flack wrote:

Next question: the "currently" in that comment suggests that could change,
but is there any present intention to change it, or is this likely to just
be the way it is for the foreseeable future?

Some related patches and discussions:

* ICU as default collation provider
https://commitfest.postgresql.org/21/1543/

* ICU for global collation
https://commitfest.postgresql.org/25/2256/

Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: https://www.manitou-mail.org
Twitter: @DanielVerite