Re: ICU, locale and collation question - Mailing list pgsql-general

From Peter Eisentraut
Subject Re: ICU, locale and collation question
Date
Msg-id e581e338-deea-2901-aa37-bf882077c377@enterprisedb.com
Whole thread Raw
In response to Re: ICU, locale and collation question  (Oscar Carlberg <oscar.carlberg@fortnox.se>)
Responses Re: ICU, locale and collation question
List pgsql-general
On 09.05.23 08:54, Oscar Carlberg wrote:
> Our initdb setup would then look like this for compatibility;
> -E 'UTF-8'
> --locale-provider=icu
> --icu-locale=sv-SE-x-icu
> --lc_monetary=sv_SE.UTF-8
> --lc-numeric=sv_SE.UTF-8
> --lc-time=sv_SE.UTF-8
> --lc-messages=en_US.UTF-8
> 
> Should we still provide createdb with --lc-collate=C and --lc-ctype=C, 
> or should we set those to sv_SE.UTF-8 as well?

You should set those to something other than C.  It doesn't matter much 
what exactly, so what you have there is fine.

Setting it to C would for example affect the ability of the text search 
functionality to detect words containing non-ASCII characters.




pgsql-general by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: ICU, locale and collation question
Next
From: Steven Lembark
Date:
Subject: Re: Return rows in input array's order?