Re: ICU for global collation

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Marina Polyakova <m(dot)polyakova(at)postgrespro(dot)ru>
Cc: pgsql-hackers(at)postgresql(dot)org, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pryzby(at)telsasoft(dot)com, rjuju123(at)gmail(dot)com, daniel(at)manitou-mail(dot)org, AndrewBille(at)gmail(dot)com, peter(dot)eisentraut(at)enterprisedb(dot)com
Subject: Re: ICU for global collation
Date: 2022-11-01 07:03:11
Message-ID: Y2DEr8etSDdw5e/
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Fri, Oct 21, 2022 at 05:32:38PM +0300, Marina Polyakova wrote:
> Hello!
> I discovered an interesting behaviour during installcheck runs when the
> cluster was initialized with ICU locale provider:
> $ initdb --locale-provider icu --icu-locale en-US -D data &&
> 2) The option --no-locale in pg_regress is described as "use C locale" [2].
> But in this case the created databases actually use the ICU locale provider
> with the ICU cluster locale from template0 (see
> diff_check_backend_used_provider.patch):
> $ make NO_LOCALE=1 installcheck

Yes, this looks wrong on the ground on what -no-locale is expected to
do, aka use a C locale. Peter?

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2022-11-01 07:16:51 Re: heavily contended lwlocks with long wait queues scale badly
Previous Message Michael Paquier 2022-11-01 05:55:33 Re: [patch] Have psql's \d+ indicate foreign partitions