| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | "Peter Eisentraut" <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>,kaleb(dot)akalework(at)asg(dot)com,pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15651: Collation setting en_US.utf8 breaking sort order |
| Date: | 2019-02-23 17:30:01 |
| Message-ID: | 9cbd8ba7-899f-4ed3-92b1-902b0d2456ae@manitou-mail.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Peter Eisentraut wrote:
> With ICU (COLLATE "und-x-icu"), I get the line with the space first. I
> took a bit of a look around the various Unicode documents and I don't
> find anything that would defend the glibc behavior.
The glibc result is now version-dependent. With glibc-2.28,
on Debian buster:
buster$ LC_COLLATE=en_US.utf8 sort stuff.txt
~!(at)#$^&(
AAA
BAA
CAA
buster$ apt-cache show libc-bin | grep Version
Version: 2.28-7
As opposed to the current Debian stable, with glibc-2.24:
stretch$ LC_COLLATE=en_US.utf8 sort stuff.txt
~!(at)#$^&(
AAA
BAA
CAA
DAA
stretch$ apt-cache show libc-bin|grep Version
Version: 2.24-11+deb9u3
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Verite | 2019-02-23 17:48:55 | RE: BUG #15651: Collation setting en_US.utf8 breaking sort order |
| Previous Message | Peter Eisentraut | 2019-02-23 08:36:39 | Re: BUG #15651: Collation setting en_US.utf8 breaking sort order |