Re: pgsql: Add standard collation UNICODE

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: 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-10 19:52:22
Message-ID: 6648546F-52B6-4525-A13B-414D99655033@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers


> On Mar 10, 2023, at 11:44 AM, Jeff Davis <pgsql(at)j-davis(dot)com> 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.

Do you have any customizations or other tests in
place for adjusting the collation ordering that
could be affecting the local build? The capitals
should be first. I can try my own local test in a bit.

Jonathan

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Jeff Davis 2023-03-10 21:24:27 Re: pgsql: Add standard collation UNICODE
Previous Message Jeff Davis 2023-03-10 19:44:08 Re: pgsql: Add standard collation UNICODE