| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Jeremy Schneider <schneider(at)ardentperf(dot)com> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Update Unicode data to Unicode 16.0.0 |
| Date: | 2025-03-15 17:49:44 |
| Message-ID: | 2b546d5babc470f64deac43810785ee44d884440.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2025-03-14 at 23:54 -0700, Jeremy Schneider wrote:
> From my perspective, the whole point of the builtin collation was to
> one option that avoids these problems that come with updating both
> ICU
> and glibc.
>
> So I guess the main point of the builtin provider just that it's
> faster
> than ICU?
It doesn't break primary keys.
Also, it's stable within a major version, we can document and test its
behavior, it solves 99% of the upgrade problem, and what problems
remains are much more manageable.
And yes, collation is way, way faster than ICU.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean | 2025-03-15 19:28:50 | Proposal: Deferred Replica Filtering for PostgreSQL Logical Replication |
| Previous Message | Tomas Vondra | 2025-03-15 17:49:32 | Assert(TransactionIdPrecedesOrEquals(TransactionXmin, RecentXmin)); |