MIME-Version: 1.0
References: <CAFCRh--J-Ra-Y73utj9SN4koJnucAH9+7eOY4Ya-av1wtv3pqg@mail.gmail.com>
 <5da10da1-c842-43fa-acf8-98a1fe8ddcfd@manitou-mail.org>
In-Reply-To: <5da10da1-c842-43fa-acf8-98a1fe8ddcfd@manitou-mail.org>
From: Dominique Devienne <ddevienne@gmail.com>
Date: Thu, 5 Jun 2025 17:40:04 +0200
Message-ID: <CAFCRh-8KoLDppV0K21rLZc=dR9_hgvzgoYf=g5PszbARKZ9RjQ@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-8KoLDppV0K21rLZc%3DdR9_hgvzgoYf%3Dg5PszbARKZ9RjQ%40mail.gmail.com>
Precedence: bulk

On Thu, Jun 5, 2025 at 5:01=E2=80=AFPM Daniel Verite <daniel@manitou-mail.o=
rg> wrote:
>         Dominique Devienne wrote:
> > >  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???
>
> Yes, definitely.
>
> But suppose your database has an extension that calls local-dependent
> code, such as strxfrm() [1] for instance.
>
> The linked MSVC doc says:
>
>  "The transformation is made using the locale's LC_COLLATE category
>  setting. For more information on LC_COLLATE, see setlocale. strxfrm
>  uses the current locale for its locale-dependent behavior"
>
> But what will be the value in LC_COLLATE when this extension code
> is running in a database using the builtin provider?
> It's the value found in pg_database.datcollate that was specified
> when creating the database with the lc_collate or locale option.
>
> The builtin provider routines are used for code inside Postgres
> core, but code outside its perimeter can still call libc functions
> that depend on lc_collate and lc_ctype.

So you're saying datcollate and datctype from pg_database are
irrelevant to PostgreSQL itself, and only extensions might be affects?

Which implies that I shouldn't worry about those differences?
Am I reading you right? --DD