Re: PostgreSQL 10 initdb with locale de-x-icu fails on Windows Server 2012 - Mailing list pgsql-bugs

From Kyotaro Horiguchi
Subject Re: PostgreSQL 10 initdb with locale de-x-icu fails on Windows Server 2012
Date
Msg-id 20220704.093405.1243358043142197360.horikyota.ntt@gmail.com
Whole thread Raw
In response to PostgreSQL 10 initdb with locale de-x-icu fails on Windows Server 2012  ("ROSESOFT S. Hoffmann" <sh@rosesoft.de>)
Responses AW: PostgreSQL 10 initdb with locale de-x-icu fails on Windows Server 2012  ("ROSESOFT S. Hoffmann" <sh@rosesoft.de>)
List pgsql-bugs
At Fri, 1 Jul 2022 13:07:13 +0000, "ROSESOFT S. Hoffmann" <sh@rosesoft.de> wrote in
> initdb.exe .. -E UTF8 --locale=de-x-icu --text-search-config=german ..
>
> Error message:
> initdb: ungültiger Locale-Name »de-x-icu«

> According to https://www.postgresql.org/download/windows/ PostgreSQL
> 10 is supported by Windows Server 2012.

If you are unfortunately using PostgreSQL 10, it doesn't support ICU
collations as the default for databases.  It's a new feature of 15.

https://www.postgresql.org/docs/15/release-15.html
> - Allow ICU collations to be set as the default for clusters and
>   databases (Peter Eisentraut)
>   Previously, ICU collations could only be specified in CREATE
>   COLLATION and used with the COLLATE clause.

If you are using PG15, --icu-locale accompanied by
--locale-provider=icu instead of --locale will work for you.

https://www.postgresql.org/docs/devel/app-initdb.html

> Alternatively, the ICU library can be used to provide locale
> services. (Again, this only sets the default for subsequently created
> databases.) To select this option, specify --locale-provider=icu. To
> choose the specific ICU locale ID to apply, use the option
> --icu-locale. Note that for implementation reasons and to support
> legacy code, initdb will still select and initialize libc locale
> settings when the ICU locale provider is used.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #17537: Dynamically updating statement_timeout not affect the insert query right now.
Next
From: "Xiong He"
Date:
Subject: Re: Auto-vacuum timing out and preventing connections