From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Doug Doole <ddoole@salesforce.com>
Cc: Craig Ringer <craig@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: ICU integration
Date: Thu, 08 Sep 2016 11:16:00 -0400
Message-ID: <3006.1473347760@sss.pgh.pa.us> (raw)
In-Reply-To: <6008673a-e371-8437-adc0-96fba4a74028@2ndquadrant.com>
References: <85364fde-091f-bbc0-fec2-e3ede39840a6@2ndquadrant.com>
<CAMsr+YE27yoX7fF40k+5swo+2cWguV0j6jtkWKj7RRowYGo9Sg@mail.gmail.com>
<f0e24354-31f1-47cd-c384-e41d72d43e83@2ndquadrant.com>
<51759C7D-BE9E-4173-B5F9-EFD7B9594C2B@salesforce.com>
<f0adba2a-0846-cbbc-06eb-0f938c119aa9@2ndquadrant.com>
<CAP6UvaNTvYXmsJTiDQKwKTBJhO-axRXBjWTXJ5oAonSFNJ514g@mail.gmail.com>
<6008673a-e371-8437-adc0-96fba4a74028@2ndquadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 9/6/16 1:40 PM, Doug Doole wrote:
>> We carried the ICU version numbers around on our collation and locale
>> IDs (such as fr_FR%icu36) . The database would load multiple versions of
>> the ICU library so that something created with ICU 3.6 would always be
>> processed with ICU 3.6. This avoided the problems of trying to change
>> the rules on the user. (We'd always intended to provide tooling to allow
>> the user to move an existing object up to a newer version of ICU, but we
>> never got around to doing it.) In the code, this meant we were
>> explicitly calling the versioned API so that we could keep the calls
>> straight.
> I understand that in principle, but I don't see operating system
> providers shipping a bunch of ICU versions to facilitate that. They
> will usually ship one.
I agree with that estimate, and I would further venture that even if we
wanted to bundle ICU into our tarballs, distributors would rip it out
again on security grounds. I am dead certain Red Hat would do so; less
sure that other vendors have similar policies, but it seems likely.
They don't want to have to fix security bugs in more than one place.
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.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter.eisentraut@2ndquadrant.com, ddoole@salesforce.com, craig@2ndquadrant.com
Subject: Re: ICU integration
In-Reply-To: <3006.1473347760@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox