| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, 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:10:02 |
| Message-ID: | 1605453.1678651802@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Andrew Dunstan <andrew(at)dunslane(dot)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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2023-03-12 22:47:32 | Re: pgsql: Add standard collation UNICODE |
| Previous Message | Andrew Dunstan | 2023-03-12 20:04:55 | Re: pgsql: Add standard collation UNICODE |