4 ms·
The post of from 2014 FYI. No idea if this is still an issue.
by bmurphy1976 8y ago
The post of from 2014 FYI. No idea if this is still an issue.
- daamien 8y agoThis is still an issue : https://postgresql.verite.pro/blog/2018/08/27/glibc-upgrade.html https://postgresql.verite.pro/blog/2018/08/27/glibc-upgrade....
- JadeNB 8y agonezirus (https://news.ycombinator.com/item?id=18855711 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 https://news.ycombinator.com/item?id=18855837) contrary reply.)
- nezirus 8y agoArch 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.html 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)
- tssva 8y agoPostgresql 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.