From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Craig Ringer <craig@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: ICU integration
Date: Wed, 31 Aug 2016 00:12:34 -0400
Message-ID: <f0e24354-31f1-47cd-c384-e41d72d43e83@2ndquadrant.com> (raw)
In-Reply-To: <CAMsr+YE27yoX7fF40k+5swo+2cWguV0j6jtkWKj7RRowYGo9Sg@mail.gmail.com>
References: <85364fde-091f-bbc0-fec2-e3ede39840a6@2ndquadrant.com>
<CAMsr+YE27yoX7fF40k+5swo+2cWguV0j6jtkWKj7RRowYGo9Sg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 8/30/16 11:27 PM, Craig Ringer wrote:
> Speaking of which, have you had a chance to try it on Windows yet?
nope
> How stable are the UCU locales? Most importantly, does ICU offer any
> way to "pin" a locale version, so we can say "we want de_DE as it was
> in ICU 4.6" and get consistent behaviour when the user sets up a
> replica on some other system with ICU 4.8? Even if the German
> government has changed its mind (again) about some details of the
> language and 4.8 knows about the changes but 4.4 doesn't?
I forgot to mention this, but the patch adds a collversion column that
stores the collation version (provided by ICU). And then when you
upgrade ICU to something incompatible you get
+ if (numversion != collform->collversion)
+ ereport(WARNING,
+ (errmsg("ICU collator version mismatch"),
+ errdetail("The database was created using
version 0x%08X, the library provides version 0x%08X.",
+ (uint32) collform->collversion,
(uint32) numversion),
+ errhint("Rebuild affected indexes, or build
PostgreSQL with the right version of ICU.")));
So you still need to manage this carefully, but at least you have a
chance to learn about it.
Suggestions for refining this are welcome.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
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: peter.eisentraut@2ndquadrant.com, craig@2ndquadrant.com
Subject: Re: ICU integration
In-Reply-To: <f0e24354-31f1-47cd-c384-e41d72d43e83@2ndquadrant.com>
* 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