From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ICU for global collation |
Date: | 2019-08-21 07:23:50 |
Message-ID: | 99faa8eb-9de2-8ec0-0a25-1ad1276167cc@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2019-08-21 08:56, Andrey Borodin wrote:
> postgres=# create database a template template0 collation_provider icu lc_collate 'en_US.utf8';
> CREATE DATABASE
> postgres=# \c a
> 2019-08-21 11:43:40.379 +05 [41509] FATAL: collations with different collate and ctype values are not supported by ICU
> FATAL: collations with different collate and ctype values are not supported by ICU
Try
create database a template template0 collation_provider icu locale
'en_US.utf8';
which sets both lc_collate and lc_ctype. But 'en_US.utf8' is not a
valid ICU locale name. Perhaps use 'en' or 'en-US'.
I'm making a note that we should prevent creating a database with a
faulty locale configuration in the first place instead of failing when
we're connecting.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2019-08-21 07:32:38 | Re: [HACKERS] WAL logging problem in 9.4.3? |
Previous Message | Peter Eisentraut | 2019-08-21 07:18:50 | Re: some SCRAM read_any_attr() confusion |