News for hackers. Stuff that matters.

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

Re:The dangers of streaming across versions of glibc: A caut... by bmurphy1976 on Tuesday January 08, 2019 @09:40AM (#18855742)
The post of from 2014 FYI. No idea if this is still an issue.
[ Parent | on HN ]
Re:The dangers of streaming across versions of glibc: A caut... by daamien on Tuesday January 08, 2019 @09:54AM (#18855837)
This is still an issue :

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

[ Parent | on HN ]
Re:The dangers of streaming across versions of glibc: A caut... by JadeNB on Tuesday January 08, 2019 @09:57AM (#18855862)
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.)
[ Parent | on HN ]
Re:The dangers of streaming across versions of glibc: A caut... by nezirus on Tuesday January 08, 2019 @10:19AM (#18856044)
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)
[ Parent | on HN ]
Re:The dangers of streaming across versions of glibc: A caut... by tssva on Tuesday January 08, 2019 @10:23AM (#18856091)
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.
[ Parent | on HN ]