Re: ICU for global collation - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: ICU for global collation
Date
Msg-id 65ef1a8a-1fc3-3dc3-c7aa-6b9f649014b2@enterprisedb.com
Whole thread Raw
In response to Re: ICU for global collation  (Marina Polyakova <m.polyakova@postgrespro.ru>)
Responses Re: ICU for global collation
List pgsql-hackers
On 16.09.22 08:49, Marina Polyakova wrote:
> But perhaps the check that --icu-locale cannot be specified unless 
> locale provider icu is chosen should also be moved here? So all these 
> checks will be in one place and it will use the provider from the 
> template database (which could be icu):
> 
> $ initdb --locale-provider icu --icu-locale en-US -D data &&
> pg_ctl -D data -l logfile start &&
> createdb --icu-locale ru-RU --template template0 mydb
> ...
> createdb: error: database creation failed: ERROR:  ICU locale cannot be 
> specified unless locale provider is ICU

Can you be more specific about what you are proposing here?  I'm not 
following.




pgsql-hackers by date:

Previous
From: "houzj.fnst@fujitsu.com"
Date:
Subject: RE: why can't a table be part of the same publication as its schema
Next
From: Nathan Bossart
Date:
Subject: introduce optimized linear search functions that return index of matching element