Re: [HACKERS] [GENERAL] Not able to create collation on Windows - Mailing list pgsql-hackers

From Murtuza Zabuawala
Subject Re: [HACKERS] [GENERAL] Not able to create collation on Windows
Date
Msg-id CAKKotZTZw9dAicmxB6j5sApcehtP3_JWEJa-WnRJaix80peWYQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] [GENERAL] Not able to create collation on Windows  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] [GENERAL] Not able to create collation on Windows  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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 <tgl@sss.pgh.pa.us> wrote:
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> 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 library does not support that.  I'm not convinced about that.

Uh, we already do.  Note all the regression tests that unconditionally
assume that the POSIX collation works.  Also, I am confused by your
apparent belief that there might somewhere be a version of libc that
fails to provide C-locale-compliant behavior.  Surely nobody would
tolerate a version of strcmp() that fails to act per C spec.

                        regards, tom lane

pgsql-hackers by date:

Previous
From: "Tels"
Date:
Subject: Re: [HACKERS] PL_stashcache, or, what's our minimum Perl version?
Next
From: Amit Khandekar
Date:
Subject: Re: [HACKERS] map_partition_varattnos() and whole-row vars