From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | Richard Huxton <dev(at)archonet(dot)com>, Csaba Nagy <nagy(at)ecircle-ag(dot)com>, Mage <mage(at)mage(dot)hu>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: is this a bug or I am blind? |
Date: | 2005-12-15 22:18:16 |
Message-ID: | 17448.1134685096@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> But then I thought of another idea. What if Postgres just used strxfrm()
> instead of strcoll everywhere? Then it ought to never produce inconsistent
> results. At least if strxfrm() doesn't just return randomly varying results
> for the same inputs.
AFAICS the most that could accomplish is to make failures more obvious;
it wouldn't actually fix anything. I don't think that's worth the
runtime penalty it would incur.
What we *ought* to be doing is trying to figure a way to detect and
disallow inconsistent locale/encoding combinations. We've avoided that
because there seems no general platform-independent way to find out the
encoding expected by a locale. But surely we could manage to make it
work at least on glibc and Windows, which would be a step ahead of doing
nothing.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2005-12-15 22:43:02 | Re: Timestamp <-> ctime conversion question ... |
Previous Message | Greg Stark | 2005-12-15 21:55:15 | Re: is this a bug or I am blind? |