| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Doug Doole <ddoole(at)salesforce(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ICU integration |
| Date: | 2016-09-08 16:19:39 |
| Message-ID: | 9caee847-7a64-a71a-d4ce-a269b04a3a8c@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/8/16 11:16 AM, Tom Lane wrote:
> This is a problem, if ICU won't guarantee cross-version compatibility,
> because it destroys the argument that moving to ICU would offer us
> collation behavior stability.
It would offer a significant upgrade over the current situation.
First, it offers stability inside the same version. Whereas glibc might
change a collation in a minor upgrade, ICU won't do that. And the
postgres binary is bound to a major version of ICU by the soname (which
changes with every major release). So this would avoid the situation
that a simple OS update could break collations.
Second, it offers a way to detect that something has changed. With
glibc, you don't know anything unless you read the source diffs. With
ICU, you can compare the collation version before and after and at least
tell the user that they need to refresh indexes or whatever.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Verite | 2016-09-08 16:25:09 | Re: Surprising behaviour of \set AUTOCOMMIT ON |
| Previous Message | Peter Eisentraut | 2016-09-08 16:12:49 | Re: Forbid use of LF and CR characters in database and role names |