| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Jeremy Schneider <schneider(at)ardentperf(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Noah Misch <noah(at)leadboat(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [18] Policy on IMMUTABLE functions and Unicode updates |
| Date: | 2024-07-23 20:34:00 |
| Message-ID: | f5cf0d35-4fa8-40f5-a6e6-207c3e921b48@manitou-mail.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> > I don't see how we can get by without some kind of versioning here.
> > It's probably too late to do that for v17,
>
> Why? If we agree that that's the way forward, we could certainly
> stick some collversion other than "1" into pg_c_utf8's pg_collation
> entry. There's already been one v17 catversion bump since beta2
> (716bd12d2), so another one is basically free.
pg_collation.collversion has been used so far for the sort part
of the collations.
For the ctype part:
postgres=# select unicode_version();
unicode_version
-----------------
15.1
(1 row)
postgres=# select icu_unicode_version ();
icu_unicode_version
---------------------
14.0
(1 row)
Best regards,
--
Daniel Vérité
https://postgresql.verite.pro/
Twitter: @DanielVerite
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2024-07-23 20:36:12 | Re: [18] Policy on IMMUTABLE functions and Unicode updates |
| Previous Message | Tom Lane | 2024-07-23 20:28:26 | Re: [18] Policy on IMMUTABLE functions and Unicode updates |