From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> |
Cc: | 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-07 13:25:25 |
Message-ID: | 22685.1444224325@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> writes:
> At the risk of getting flamed: I think that this is a bug in
> PostgreSQL, not CentOS. I've said why I think that is at least once
> already [1]. Simply put, there is no justification for the belief that
> some people have that collations should be immutable, and there is
> some justification for OS vendors updating them in a way that
> disregards our use of the collations. Glibc actually versions
> collations, although that isn't in any standard, and it isn't clear
> that we can benefit from that beyond refusing to start the server when
> a collation was superseded by a new version.
I can think of less helpful responses to such a situation, but not easily.
The only real way out of such a situation is to REINDEX affected indexes.
Refusing to start the server not only doesn't contribute to a solution,
but makes it impossible to fix manually.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hellmuth Vargas | 2015-10-07 13:46:05 | Re: ayuda con funcion List |
Previous Message | Andrus | 2015-10-07 12:12:38 | Re: How to drop user if objects depend on it |