Re: pgsql: Add standard collation UNICODE - Mailing list pgsql-committers

From Andrew Dunstan
Subject Re: pgsql: Add standard collation UNICODE
Date
Msg-id c05d7d71-e869-f6ae-b83c-2d5cab0a0dc4@dunslane.net
Whole thread Raw
In response to Re: pgsql: Add standard collation UNICODE  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: pgsql: Add standard collation UNICODE  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-committers


On 2023-03-10 Fr 14:44, Jeff Davis wrote:
On Fri, 2023-03-10 at 12:42 +0000, Peter Eisentraut wrote:
Add standard collation UNICODE
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2023-03-10%2018%3A58%3A04

Looks like there's still a failure, even after subsequent fix
3e623ebc7a. I'm wondering how that diff happens, because I tested all
versions of ICU between 50 and 72 (except 58 and 59, where I had build
problems) and 'abc' is always less than 'ABC' in the root locale.

Must be something simple I'm missing.



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


I'll see about updating the machine (probably by recreating it with a modern AMI)


cheers


andrew

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

pgsql-committers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: pgsql: Add standard collation UNICODE
Next
From: Tom Lane
Date:
Subject: pgsql: Fix misbehavior in contrib/pg_trgm with an unsatisfiable regex.