On 7/25/17 15:20, Victor Wagner wrote: > It turns out, that PostgreSQL enumerates collations for all ICU locales > and passes it into uloc_toLanguageTag function with strict argument of > this function set to TRUE. But for some locales > (es*@collation=tradtiional, si*@collation=dictionary) only call with > strict=FALSE succeeds in ICU 4.2. In newer versions of ICU all locales > can be resolved with strict=TRUE.
We are only calling uloc_toLanguageTag() with keyword/value combinations that ICU itself previously told us were supported. So just ignoring errors doesn't seem proper in this case. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers