RE: BUG #15651: Collation setting en_US.utf8 breaking sort order

From: Kaleb Akalework <kaleb(dot)akalework(at)asg(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: RE: BUG #15651: Collation setting en_US.utf8 breaking sort order
Date: 2019-02-22 19:17:06
Message-ID: 9421be5798da48c0a265bc13b0ef5224@asg.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Ok so if this is intended behavior of UTF8 then I understand. My last question then would be if I use a collation setting of C, does it mean I won't be able to support multiple languages?

-----Original Message-----
From: Peter Geoghegan <pg(at)bowt(dot)ie>
Sent: Friday, February 22, 2019 1:41 PM
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kaleb Akalework <kaleb(dot)akalework(at)asg(dot)com>; PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15651: Collation setting en_US.utf8 breaking sort order

*** External email: Verify sender before opening attachments or links ***

On Fri, Feb 22, 2019 at 10:03 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> This appears to be the intended behavior of en_US sorting.

Right. UCA style algorithms tend to give the least weight of all to whitespace characters. They're tertiary weight, if memory serves.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-02-22 19:53:58 Re: BUG #15651: Collation setting en_US.utf8 breaking sort order
Previous Message Peter Geoghegan 2019-02-22 18:40:58 Re: BUG #15651: Collation setting en_US.utf8 breaking sort order