| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Joe Conway <mail(at)joeconway(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Update Unicode data to Unicode 16.0.0 |
| Date: | 2025-01-20 21:39:35 |
| Message-ID: | 9959adcd0ac5ed6ff8dd808c4008f659955e018a.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2024-11-15 at 17:09 +0100, Peter Eisentraut wrote:
> The practice of regularly updating the Unicode files is older than
> the
> builtin collation provider. It is similar to updating the time zone
> files, the encoding conversion files, the snowball files, etc. We
> need
> to move all of these things forward to keep up with the aspects of
> the
> real world that this data reflects.
Should we consider bundling multiple versions of the generated tables
(header files) along with Postgres?
That would enable a compile-time option to build with an older version
of Unicode if you want, solving the packager concern that Noah raised.
It would also make it easier for people to coordinate the Postgres
version of Unicode and the ICU version of Unicode.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2025-01-20 21:39:40 | Re: [PATCH] Improve code coverage of network address functions |
| Previous Message | Michail Nikolaev | 2025-01-20 21:35:53 | Re: [BUG?] check_exclusion_or_unique_constraint false negative |