"Timur Luchkin" <timur.luchkin@gmail.com> writes:
> I have a table (dictionary) with international data in many languages.
> After the migration to the new hardware the 'analyze' operation instead
> of 5 seconds takes 3-5 minutes now (with 100% cpu core usage).
> Investigation showed that slow performance introduced by new glibc.
> Previous versions of glibc (2.15 - 2.16) works fine, new versions (2.22
> and 2.23) have this problem (versions between 2.17 and 2.21 were not
> tested).
So ... why do you think this is a Postgres bug and not a glibc bug?
We have no control over what happens inside strcoll().
regards, tom lane
