Re: LOCALE C.UTF-8 on EDB Windows v17 server

2025-06-05 Thread Jeff Davis
On Thu, 2025-06-05 at 10:53 +0200, Dominique Devienne wrote: > If locale_provider is builtin, then locale or builtin_locale must be > specified and set to either C or C.UTF-8. > > It clearly says "locale or builtin_locale", emphasis on the OR. > > So two issues here. > 1) the doc is wrong or misl

Re: LOCALE C.UTF-8 on EDB Windows v17 server

2025-06-05 Thread Jeff Davis
On Thu, 2025-06-05 at 15:07 +0200, Dominique Devienne wrote: > But isn't the point of the new-in-v17 builtin provider is to be > system > independent??? Yes, a major part of the builtin provider is complete consistency across platforms for the entire collation system -- anything affected by the da

Re: LOCALE C.UTF-8 on EDB Windows v17 server

2025-06-05 Thread Daniel Verite
Dominique Devienne wrote: > So you're saying datcollate and datctype from pg_database are > irrelevant to PostgreSQL itself, and only extensions might be affects? Almost. An exception that still exists in v18, as far as I can see [1], is the default full text search parser still using lib

Re: LOCALE C.UTF-8 on EDB Windows v17 server

2025-06-05 Thread Jeff Davis
On Thu, 2025-06-05 at 11:34 +0200, Dominique Devienne wrote: > On Thu, Jun 5, 2025 at 11:07 AM Dominique Devienne > wrote: > > So... It is possible to have the SAME command on Windows and Linux, > > which yields the SAME datcollate and datctype values??? > > So far, such a command eludes me, I'm a

Re: LOCALE C.UTF-8 on EDB Windows v17 server

2025-06-05 Thread Dominique Devienne
On Thu, Jun 5, 2025 at 5:01 PM Daniel Verite 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 > >

Re: LOCALE C.UTF-8 on EDB Windows v17 server

2025-06-05 Thread Daniel Verite
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 o

Re: LOCALE C.UTF-8 on EDB Windows v17 server

2025-06-05 Thread Dominique Devienne
On Thu, Jun 5, 2025 at 2:40 PM Daniel Verite 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 datloca

Re: LOCALE C.UTF-8 on EDB Windows v17 server

2025-06-05 Thread Daniel Verite
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

Re: LOCALE C.UTF-8 on EDB Windows v17 server

2025-06-05 Thread Dominique Devienne
On Thu, Jun 5, 2025 at 1:40 PM Laurenz Albe wrote: > On Thu, 2025-06-05 at 10:53 +0200, Dominique Devienne wrote: > > It clearly says "locale or builtin_locale", emphasis on the OR. > > You are right, and that's how it works on Linux. > BUILTIN_LOCALE is not required. Still, required or not, they

Re: LOCALE C.UTF-8 on EDB Windows v17 server

2025-06-05 Thread Laurenz Albe
On Thu, 2025-06-05 at 10:53 +0200, Dominique Devienne wrote: > Thanks Laurenz. Indeed, Using LOCALE vs BUILTIN_LOCALE matters. > > 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

Re: LOCALE C.UTF-8 on EDB Windows v17 server

2025-06-05 Thread Dominique Devienne
On Thu, Jun 5, 2025 at 11:07 AM Dominique Devienne wrote: > So... It is possible to have the SAME command on Windows and Linux, > which yields the SAME datcollate and datctype values??? > So far, such a command eludes me, I'm afraid. --DD So I tried to be explicit about lc_collate and lc_ctype to

Re: LOCALE C.UTF-8 on EDB Windows v17 server

2025-06-05 Thread Dominique Devienne
On Thu, Jun 5, 2025 at 4:52 AM Jeff Davis wrote: > > On Windows, I'm getting > I tried on windows and linux and got the same result. Thanks Jeff, for your informative email. The command work, just like it does on Linux. YET... The results are NOT the same! C:\Users\ddevienne>psql service=my17 ps

Re: LOCALE C.UTF-8 on EDB Windows v17 server

2025-06-05 Thread Dominique Devienne
On Thu, Jun 5, 2025 at 3:01 AM Laurenz Albe wrote: > On Wed, 2025-06-04 at 14:23 +0200, Dominique Devienne wrote: > > The command I'm using (from a libpq trace) is: > > > > create database "dd_v168" encoding 'UTF8' locale 'C.UTF-8' > > locale_provider 'builtin' template template0 > > > > On Window

Re: LOCALE C.UTF-8 on EDB Windows v17 server

2025-06-04 Thread Jeff Davis
On Wed, 2025-06-04 at 14:23 +0200, Dominique Devienne wrote: > create database "dd_v168" encoding 'UTF8' locale 'C.UTF-8' > locale_provider 'builtin' template template0 I believe what you want is: create database "dd_v168" encoding 'UTF8' builtin_locale 'C.UTF-8' locale_provider 'builtin' tem

Re: LOCALE C.UTF-8 on EDB Windows v17 server

2025-06-04 Thread Laurenz Albe
On Wed, 2025-06-04 at 14:23 +0200, Dominique Devienne wrote: > The command I'm using (from a libpq trace) is: > > create database "dd_v168" encoding 'UTF8' locale 'C.UTF-8' > locale_provider 'builtin' template template0 > > On Windows, I'm getting > > 2025-06-04 14:07:41.227419 B 155 ErrorRespon