Re: pgsql: Add standard collation UNICODE

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Add standard collation UNICODE
Date: 2023-03-12 20:04:55
Message-ID: 98810acf-c2ea-ed90-2b5f-c8cfa6c1654f@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers


On 2023-03-11 Sa 15:47, Tom Lane wrote:
> Jeff Davis<pgsql(at)j-davis(dot)com> writes:
>> On Sat, 2023-03-11 at 08:31 -0500, Andrew Dunstan wrote:
>>> It's fairly old:
>>> $ rpm -q -a | grep icu
>>>  libicu-50.2-4.0.amzn1.x86_64
>>>  libicu-devel-50.2-4.0.amzn1.x86_64
>> FWIW I tried ICU 50.2 (built from sources) and the root locale still
>> sorts lowercase first.
> snapper is showing this failure too [1], which makes me wonder if it's
> a locally-customizable option.
>
> In general, I see no good reason for our regression tests to be making
> assumptions about exactly how ICU's root locale behaves, so I'd suggest
> just lobotomizing this test case so it doesn't depend on upper/lower
> sort order.
>
>

Yeah, I think we've found enough cases in old still not dead distros to
make this reasonable.

cheers

andrew

--
Andrew Dunstan
EDB:https://www.enterprisedb.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2023-03-12 20:10:02 Re: pgsql: Add standard collation UNICODE
Previous Message Tom Lane 2023-03-12 18:20:48 pgsql: Work around implementation restriction in adjust_appendrel_attrs