From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [GENERAL] Not able to create collation on Windows |
Date: | 2017-08-01 15:39:43 |
Message-ID: | 24826.1501601983@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2017-08-01 16:13:33 | Re: Perfomance of IN-clause with many elements and possible solutions |
Previous Message | Peter Eisentraut | 2017-08-01 15:35:38 | Re: [GENERAL] Not able to create collation on Windows |
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2017-08-01 15:59:47 | Re: Possible bug in 9.3.17 using operator <> |
Previous Message | Nick Dro | 2017-08-01 15:39:35 | Possible bug in 9.3.17 using operator <> |