From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: ICU for global collation
Date: Wed, 21 Aug 2019 09:23:50 +0200
Message-ID: <99faa8eb-9de2-8ec0-0a25-1ad1276167cc@2ndquadrant.com> (raw)
In-Reply-To: <53008C67-AA12-4CE8-9DEC-C21B9E1D57A8@yandex-team.ru>
References: <5e756dd6-0e91-d778-96fd-b1bcb06c161a@2ndquadrant.com>
<53008C67-AA12-4CE8-9DEC-C21B9E1D57A8@yandex-team.ru>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, x4mmm@yandex-team.ru
Subject: Re: ICU for global collation
In-Reply-To: <99faa8eb-9de2-8ec0-0a25-1ad1276167cc@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox