Re: BUG #15651: Collation setting en_US.utf8 breaking sort order - Mailing list pgsql-bugs

From Peter Eisentraut
Subject Re: BUG #15651: Collation setting en_US.utf8 breaking sort order
Date
Msg-id 1f6f60bf-79a4-b739-5e04-8360085cf3d8@2ndquadrant.com
Whole thread Raw
In response to Re: BUG #15651: Collation setting en_US.utf8 breaking sort order  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #15651: Collation setting en_US.utf8 breaking sort order  ("Daniel Verite" <daniel@manitou-mail.org>)
List pgsql-bugs
On 2019-02-22 19:03, Tom Lane wrote:
> $ LANG=en_US sort stuff.txt 
> ~!@#$^&(
>  
> AAA
> BAA
> CAA
> DAA

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.

<obscure detail>
However, since some of those special characters are variable collating
elements and some are not, there might well be an explanation.
</obscure detail>

So, maybe try ICU.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #15636: PostgreSQL 11.1 pg_basebackup backup to a CIFSdestination throws fsync error at end of backup
Next
From: "Daniel Verite"
Date:
Subject: Re: BUG #15651: Collation setting en_US.utf8 breaking sort order