Re: locale & glibc 2.2.2

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> teg(at)redhat(dot)com (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) writes:
> > Of course not, it's not a bug - if this is a problem, it's a bug in
> > Postgresql:
>
> If glibc 2.2.2 sorts that way in C locale, then glibc is broken.
> But I assume you meant this is the behavior in some other locale.

[teg(at)halden teg]$ LC_COLLATE=C sort foo2.txt
Ad
ac
ae
[teg(at)halden teg]$

I agree that the above is far from ideal, but this is the traditional
C way. The standard locales (used everywhere, in US en_US is used
which does give you the correct order) don't have this problem, they
sort correctly:

[teg(at)halden teg]$ LC_COLLATE=en_US sort foo2.txt
ac
Ad
ae
[teg(at)halden teg]$

--
Trond Eivind Glomsrød
Red Hat, Inc.