Re: Order changes in PG16 since ICU introduction - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Order changes in PG16 since ICU introduction
Date
Msg-id 317a5e27ce8c4be91ae3c3b193c4e10a2f112190.camel@j-davis.com
Whole thread Raw
In response to Re: Order changes in PG16 since ICU introduction  ("Daniel Verite" <daniel@manitou-mail.org>)
Responses Re: Order changes in PG16 since ICU introduction
Re: Order changes in PG16 since ICU introduction
List pgsql-hackers
On Wed, 2023-06-07 at 23:50 +0200, Daniel Verite wrote:
> The simplest way to obtain that in v16 is to teach initdb that
> --locale=C without the --locale-provider option implies that
> --locale-provider=libc ([1])

As I replied in that subthread, that creates a worse problem: if you
only change the provider when the locale is C, then what about when the
locale is *not* C?

  export LANG=en_US.UTF-8
  initdb -D data --locale=fr_FR.UTF-8
  ...
    provider:    icu
    ICU locale:  en-US

I believe that case is an order of magnitude worse than the other cases
you brought up in that subthread.

It also leaves the fundamental problem in place that LOCALE only
applies to the libc provider, which multiple people have agreed is not
acceptable.


Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: "Fujii.Yuki@df.MitsubishiElectric.co.jp"
Date:
Subject: RE: Partial aggregates pushdown
Next
From: Noah Misch
Date:
Subject: win32ver data in meson-built postgres.exe