From: Andrew Dunstan <andrew@dunslane.net>
To: Thomas Munro <thomas.munro@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jeff Davis <pgsql@j-davis.com>
Cc: Peter Eisentraut <peter@eisentraut.org>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Add standard collation UNICODE
Date: Mon, 13 Mar 2023 14:58:34 -0400
Message-ID: <e4c2229f-939d-1c4f-dabf-c2780cb1d743@dunslane.net> (raw)
In-Reply-To: <CA+hUKGLmKe1KMhiU4nwcq-d-V7MWec8NVjCivnq6tHyQUdQwfg@mail.gmail.com>
References: <E1pac4x-002qVH-Ce@gemulon.postgresql.org>
<582e43d0a814e09c62ea662dd851f43bfc137a16.camel@j-davis.com>
<c05d7d71-e869-f6ae-b83c-2d5cab0a0dc4@dunslane.net>
<231acf388c37597a9f0f8a3af9a899df99c28e1d.camel@j-davis.com>
<1253026.1678567661@sss.pgh.pa.us>
<98810acf-c2ea-ed90-2b5f-c8cfa6c1654f@dunslane.net>
<1605453.1678651802@sss.pgh.pa.us>
<CA+hUKGLmKe1KMhiU4nwcq-d-V7MWec8NVjCivnq6tHyQUdQwfg@mail.gmail.com>
On 2023-03-12 Su 18:47, Thomas Munro wrote:
> On Mon, Mar 13, 2023 at 9:10 AM Tom Lane<tgl@sss.pgh.pa.us> wrote:
>> Andrew Dunstan<andrew@dunslane.net> writes:
>>> On 2023-03-11 Sa 15:47, Tom Lane wrote:
>>>> 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.
>> I see topminnow is showing the symptom too, so it's now pretty clear
>> that this was once a common behavior. I dug in ICU's release notes
>> and couldn't find anything about it, but they must've changed something
>> somewhen.
> Most odd, and a bit worrying for the multi-lib concept we were
> discussing (now for 17), though not fatal if it's something like
> "there was one historical screwup back in 50.whatever, but now we are
> more careful", or "it was a packaging error that was fixed but old
> systems that aren't getting updated don't have the fix", so not even
> ICU's fault (which would fit with Jeff's observation that he can't
> repro the issue by building from ICU source at the 50.2 tag, as if
> what is in the package is not what was tagged?!). It'd be nice to
> understand what happened here... What do these disagreeing systems
> report for the various version meta-data (Unicode version, CLDR
> version, the opaque collator version, etc)?
How would I discover that? Or if it's quicker I can give you access to
one or two machines which exhibit the issue.
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, thomas.munro@gmail.com, tgl@sss.pgh.pa.us, pgsql@j-davis.com, peter@eisentraut.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Add standard collation UNICODE
In-Reply-To: <e4c2229f-939d-1c4f-dabf-c2780cb1d743@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