From: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
---|---|
To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: LOCALE C.UTF-8 on EDB Windows v17 server |
Date: | 2025-06-05 13:07:49 |
Message-ID: | CAFCRh--J-Ra-Y73utj9SN4koJnucAH9+7eOY4Ya-av1wtv3pqg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jun 5, 2025 at 2:40 PM Daniel Verite <daniel(at)manitou-mail(dot)org> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Verite | 2025-06-05 15:01:52 | Re: LOCALE C.UTF-8 on EDB Windows v17 server |
Previous Message | Daniel Verite | 2025-06-05 12:40:08 | Re: LOCALE C.UTF-8 on EDB Windows v17 server |