MIME-Version: 1.0
References: <CAFCRh--iJ4MT2exvXnvRPum+7su3Jn9qmnBQqxWsAtyEyEo83A@mail.gmail.com>
 <d57d35d0-9d27-4be7-aad9-b139a18b990d@manitou-mail.org>
In-Reply-To: <d57d35d0-9d27-4be7-aad9-b139a18b990d@manitou-mail.org>
From: Dominique Devienne <ddevienne@gmail.com>
Date: Thu, 5 Jun 2025 15:07:49 +0200
Message-ID: <CAFCRh--J-Ra-Y73utj9SN4koJnucAH9+7eOY4Ya-av1wtv3pqg@mail.gmail.com>
Subject: Re: LOCALE C.UTF-8 on EDB Windows v17 server
To: Daniel Verite <daniel@manitou-mail.org>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, pgsql-general@postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAFCRh--J-Ra-Y73utj9SN4koJnucAH9%2B7eOY4Ya-av1wtv3pqg%40mail.gmail.com>
Precedence: bulk

On Thu, Jun 5, 2025 at 2:40=E2=80=AFPM Daniel Verite <daniel@manitou-mail.o=
rg> wrote:
>         Dominique Devienne wrote:
> > On Linux, no error unlike on Windows (still inconsistent there IMHO),
> > but the result is slightly different for datcollate and datctype (C vs
> > en_US),
> > while the same for datlocprovider and datlocale, what I looked at.
> >
> > Thus I kinda persist that there *is* a portability issue here.
>
> "datcollate" and "datctype" refer to operating system locale names.
>
>  locale 'C.UTF-8' or lc_collate 'C.UTF-8' lc_ctype 'C.UTF-8'
> cannot work on Windows because Windows does not have a locale
> named C.UTF-8, whereas a Linux system does (well at least recent
> Linuxes. Some old Linuxes don't).

But isn't the point of the new-in-v17 builtin provider is to be system
independent???

> What you are seeing is the effect of OS locales not being portable
> across systems. That's confusing but not a Postgres bug.

Thus builtin SHOULD be portable IMHO. --DD