From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Update Unicode data to Unicode 16.0.0 |
Date: | 2025-04-03 10:20:46 |
Message-ID: | 559e056e-719d-43bf-bb69-8aa67149c55d@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 17.03.25 19:54, Jeff Davis wrote:
> On Thu, 2025-03-13 at 14:49 +0100, Peter Eisentraut wrote:
>> I think these test result changes are incorrect. AFAICT, nothing has
>> changed in the upstream data that would explain such a change.
>>
>> I didn't get such test differences in my original patch. Did you
>> rebase
>> the patch or regenerate it? Maybe something went wrong there.
>
> Right. The previous version was improperly rebased.
>
> I went back to your original version and rebased over master (including
> the latest optimizations for case mapping), and then rebased my changes
> on top of that. Attached.
>
> One annoyance with the recent case mapping optimizations is that the
> Unicode update diff is larger, similar to the diff for
> unicode_norm_hashfunc.h. Previously, it was binary search, so the only
> differences were logical differences.
I have committed the update to the Unicode tables. I suggest you commit
your pg_upgrade patch on top of that now.
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2025-04-03 10:41:35 | Re: Making sslrootcert=system work on Windows psql |
Previous Message | Amit Langote | 2025-04-03 10:19:53 | Re: Eliminating SPI / SQL from some RI triggers - take 3 |