From: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bernd Helmle <mailings(at)oopsware(dot)de>, PGSQL Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Issues with german locale on CentOS 5,6,7 |
Date: | 2015-10-08 00:16:33 |
Message-ID: | CAEYLb_VCTw_uMfUVxfE5NV9TxwGBFuz5qSOda-vU6mcdF3LJdQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Oct 7, 2015 at 4:49 PM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
>> I agree that that would be almost as bad as carrying on, because there
>> is no reason to think that the locale thing can easily be rolled back.
>> That was my point, in fact.
>
> I have contemplated a maintenance script that would track either the
> md5 checksums of the /usr/lib/locale/*/LC_COLLATE files or the version
> of installed locale packages and automatically reindex things when
> they change (I guess after restarting the cluster to clear any glibc
> caches that might be lurking in long running backends). Or at least
> tell me that's needed. Obviously completely OS-specific...
I think we should bite the bullet and adopt ICU, without abandoning
support for OS locales for users that really need it (certainly, many
will need it initially when using pg_upgrade to get on to the first
version that happens to have ICU support). I don't like suggesting a
solution that I myself am unlikely to find the time to work on, but in
the long run that's the only sensible approach IMV.
--
Regards,
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Ramalingam, Sankarakumar | 2015-10-08 00:45:09 | Re: postgres standby won't start |
Previous Message | Adrian Klaver | 2015-10-08 00:05:51 | Re: postgres standby won't start |