From: Andrew Dunstan <andrew@dunslane.net>
To: Jeff Davis <pgsql@j-davis.com>
To: Peter Eisentraut <peter@eisentraut.org>
To: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Add standard collation UNICODE
Date: Sat, 11 Mar 2023 08:31:00 -0500
Message-ID: <c05d7d71-e869-f6ae-b83c-2d5cab0a0dc4@dunslane.net> (raw)
In-Reply-To: <582e43d0a814e09c62ea662dd851f43bfc137a16.camel@j-davis.com>
References: <E1pac4x-002qVH-Ce@gemulon.postgresql.org>
<582e43d0a814e09c62ea662dd851f43bfc137a16.camel@j-davis.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: andrew@dunslane.net, pgsql@j-davis.com, peter@eisentraut.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Add standard collation UNICODE
In-Reply-To: <c05d7d71-e869-f6ae-b83c-2d5cab0a0dc4@dunslane.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox