From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Victor Wagner <vitus(at)wagner(dot)pp(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PostgreSQL 10 (latest beta) and older ICU |
Date: | 2017-07-31 23:42:30 |
Message-ID: | 0523762c-be62-b271-226f-0771df613365@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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*(at)collation=tradtiional, si*(at)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
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2017-07-31 23:55:45 | Re: Parallel Hash take II |
Previous Message | Chapman Flack | 2017-07-31 23:13:40 | Re: [PATCH] Pattern based listeners for asynchronous messaging (LISTEN/NOTIFY) |