| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Order changes in PG16 since ICU introduction |
| Date: | 2023-06-05 17:54:58 |
| Message-ID: | 5111ffef640ec7ed5b75d9791dd18d821e96c31e.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
New patch series attached. I plan to commit 0001 and 0002 soon, unless
there are objections.
0001 causes the "C" and "POSIX" locales to be treated with
memcmp/pg_ascii semantics in ICU, just like in libc. We also considered
a new "none" provider, but it's more invasive, and we can always
reconsider that in the v17 cycle.
0002 introduces an upgrade check for users who have explicitly
requested provider=icu and iculocale=C on older versions, and rejects
upgrading from v15 in that case to avoid index corruption. Having such
a collation is almost certainly a mistake by the user, because the
collator would not give the expected memcmp semantics.
--
Jeff Davis
PostgreSQL Contributor Team - AWS
| Attachment | Content-Type | Size |
|---|---|---|
| v8-0001-ICU-support-locale-C-with-the-same-behavior-as-li.patch | text/x-patch | 11.4 KB |
| v8-0002-pg_upgrade-check-for-ICU-locale-C-in-versions-15-.patch | text/x-patch | 4.7 KB |
| v8-0003-Make-LOCALE-apply-to-ICU_LOCALE-for-CREATE-DATABA.patch | text/x-patch | 15.2 KB |
| v8-0004-Use-database-default-collation-s-provider-as-defa.patch | text/x-patch | 6.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2023-06-05 18:04:01 | Re: Let's make PostgreSQL multi-threaded |
| Previous Message | Daniel Verite | 2023-06-05 17:43:26 | Re: pg_collation.collversion for C.UTF-8 |