Re: Glibc 2.28 breaks collation for PostgreSQL (and others?)

2019-04-08 Thread Christoph Berg
Re: Paul Gevers 2019-04-06 > Regarding this PostgreSQL reindexing issue, is there anything we need to > mention in the release-notes? If this isn't fleshed out, but the most > likely answer is yes, than I'd appreciate it to receive a bug against > release-notes to remind us about it later on.

Re: Glibc 2.28 breaks collation for PostgreSQL (and others?)

2019-04-06 Thread Paul Gevers
Dear all, Regarding this PostgreSQL reindexing issue, is there anything we need to mention in the release-notes? If this isn't fleshed out, but the most likely answer is yes, than I'd appreciate it to receive a bug against release-notes to remind us about it later on. Text can come later when it

Re: Glibc 2.28 breaks collation for PostgreSQL (and others?)

2019-03-26 Thread Philipp Kern
On 3/26/2019 3:20 PM, Christoph Berg wrote: > We were thinking about doing something like that, but that doesn't > work for the general case - most libc upgrades do not break > everything, and reindexing would be overkill. It might help for the > 2.28 upgrade, but getting this to work consistently

Re: Glibc 2.28 breaks collation for PostgreSQL (and others?)

2019-03-26 Thread Christoph Berg
Re: Philipp Kern 2019-03-26 <66988de0-f9be-14c0-6b64-df64261fe...@philkern.de> > I suspect this is why MySQL keeps a whole zoo of collations internally > that never change. DB2 and Oracle bundle ICU for that reason, afaict. (But bundling software has other problems, as we all know...) > Is there

Re: Glibc 2.28 breaks collation for PostgreSQL (and others?)

2019-03-26 Thread Philipp Kern
On 3/26/2019 9:45 AM, Christoph Berg wrote: > Unfortunately not. PostgreSQL supports ICU, but not as the global > locale for clusters/databases, which is still libc only. And even if > it was supported, it's not the default, and we are still breaking all > installations. I suspect this is why

Re: Glibc 2.28 breaks collation for PostgreSQL (and others?)

2019-03-26 Thread Christoph Berg
Re: Florian Weimer 2019-03-25 <87o95yhp3h@mid.deneb.enyo.de> > > For PostgreSQL, this means that the ordering of indexes on disk is > > becoming corrupt, and all "text" (varchar, char, ...) indexes need to > > be rebuilt. (And worse, if that is not done immediately, the tables > > might become

Re: Glibc 2.28 breaks collation for PostgreSQL (and others?)

2019-03-25 Thread Florian Weimer
* Christoph Berg: > with the update to glibc 2.28, collation aka sort ordering is > changing: > > $ echo $LANG > de_DE.utf8 > $ (echo 'a-a'; echo 'a a'; echo 'a+a'; echo 'aa') | sort > > stretch: > aa > a a > a-a > a+a > > buster: > a a > a+a > a-a > aa > > A vast number of

Glibc 2.28 breaks collation for PostgreSQL (and others?)

2019-03-25 Thread Christoph Berg
Hi, with the update to glibc 2.28, collation aka sort ordering is changing: $ echo $LANG de_DE.utf8 $ (echo 'a-a'; echo 'a a'; echo 'a+a'; echo 'aa') | sort stretch: aa a a a-a a+a buster: a a a+a a-a aa A vast number of locales is affected, including en_US, possibly all of