Murtuza Zabuawala writes:
> Yes, I was able to create collation using "C" instead of "POSIX" on windows,
> CREATE COLLATION public.test from pg_catalog."C";
Yeah, I thought that might happen. So the point basically is that in
almost all of the collations code, the "C" and "POSIX" names are handl
Hi Tom,
Yes, I was able to create collation using "C" instead of "POSIX" on windows,
CREATE COLLATION public.test from pg_catalog."C";
--
Regards,
Murtuza Zabuawala
On Tue, Aug 1, 2017 at 9:09 PM, Tom Lane wrote:
> Peter Eisentraut writes:
> > On 8/1/17 10:53, Tom Lane wrote:
> >> I think th
Peter Eisentraut writes:
> On 8/1/17 10:53, Tom Lane wrote:
>> I think this is actually a bug, because the collations code clearly
>> means to allow clones of the C/POSIX locales --- see eg lc_collate_is_c,
> You seem to say that we should support a "POSIX" locale even on systems
> where the C li
On 8/1/17 10:53, Tom Lane wrote:
> Murtuza Zabuawala writes:
>> I am trying to create collation on windows using default POSIX collation
>> with pgAdmin3 but I am getting error as shown in screenshot, Can someone
>> suggest how to fix this?
>
>> *Syntax:*
>> CREATE COLLATION public.test from pg_c
Murtuza Zabuawala writes:
> I am trying to create collation on windows using default POSIX collation
> with pgAdmin3 but I am getting error as shown in screenshot, Can someone
> suggest how to fix this?
> *Syntax:*
> CREATE COLLATION public.test from pg_catalog."POSIX";
> *Error:*
> ERROR: could
