The dangers of streaming across versions of glibc: A cautionary tale (2014)

nezirus wrote: post #3

AFAIK, this is fixed in PostgreSQL 10 (ICU), so no reason to panic if you are on v10+. However, it nicely demonstrates problems with strcoll :-)

Correct. Using ICU collations avoids this problem.

Also, with libc collations you have to rebuild indexes after a glibc upgrade:

https://postgresql.verite.pro/blog/2018/08/27/glibc-upgrade....

Re: The dangers of streaming across versions of glibc: A cautionary tale (2014)

#8

Post by JadeNB » Tue, Jan 08, 2019, 2:57 PM UTC

bmurphy1976 wrote: post #4

The post of from 2014 FYI. No idea if this is still an issue.

nezirus (https://news.ycombinator.com/item?id=18855711) says it isn't. (I don't know how this squares with daamien's (https://news.ycombinator.com/item?id=18855837) contrary reply.)

Re: The dangers of streaming across versions of glibc: A cautionary tale (2014)

#9

Post by nezirus » Tue, Jan 08, 2019, 3:19 PM UTC

JadeNB wrote: post #8

bmurphy1976 wrote: post #4

The post of from 2014 FYI. No idea if this is still an issue.

nezirus ( https://news.ycombinator.com/item?id=18855711 ) says it isn't. (I don't know how this squares with daamien's ( https://news.ycombinator.com/item?id=18855837 ) contrary reply.)

Arch package is configured with ICU support, but I think you need to use ICU collations explicitly: https://postgresql.verite.pro/blog/2018/07/25/icu-extension....

  SELECT * FROM pg_catalog.pg_collation;

As usual with collations, you must be careful and know what you are doing (old collations are also still available, for backwards compatibility)

Re: The dangers of streaming across versions of glibc: A cautionary tale (2014)

#10

Post by tssva » Tue, Jan 08, 2019, 3:23 PM UTC

JadeNB wrote: post #8

bmurphy1976 wrote: post #4

The post of from 2014 FYI. No idea if this is still an issue.

nezirus ( https://news.ycombinator.com/item?id=18855711 ) says it isn't. (I don't know how this squares with daamien's ( https://news.ycombinator.com/item?id=18855837 ) contrary reply.)

Postgresql 10+ has added icu as a collation provider. If you select icu as your provider this is not an issue. If you select libc as your provider than this is still an issue you need to account for.