From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
Date: | 2017-08-18 01:22:32 |
Message-ID: | CAH2-WzmA+4Ovi=vFNRet9ap0b+Xb7qm=it1rvPnOdTYANGH1LA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Thu, Aug 17, 2017 at 6:13 PM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> On 8/14/17 23:55, Peter Geoghegan wrote:
>> pg_import_system_collations() should simply use uloc_countAvailable()
>> + uloc_getAvailable, rather than ucol_countAvailable() +
>> ucol_getAvailable().
>
> It's not clear to me that this is better. Why do we need to use a
> function that is clearly not the preferred API for this ("col" vs "loc")
> just to get more entries?
My argument for doing this is very simple: ICU/CLDR/BCP 47 provides
stability guarantees for locales, not collations [1]. For example, as
we discussed, de_BE didn't actually go away -- it just stopped being a
distinct collation within ICU, for reasons that are implementation
defined.
I admit that there are arguments against this, but by far the most
important consideration should be the stability of the names used for
pg_collation entries created during initdb.
> If we go down this route, then we'll be on
> the hook forever to keep adding more and more predefined entries by
> whatever means necessary.
Why? Locales have a mapping to various ISO codes (Country, language,
etc). It's not like new ones come along very often.
[1] https://tools.ietf.org/html/bcp47#section-3.4
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | vinod.t.v | 2017-08-18 05:18:56 | BUG #14782: VSS backup of postgres database |
Previous Message | Peter Eisentraut | 2017-08-18 01:13:18 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-08-18 01:33:32 | Re: [PATCH] Push limit to sort through a subquery |
Previous Message | Peter Eisentraut | 2017-08-18 01:22:07 | Re: Re: ICU collation variant keywords and pg_collation entries (Was: [BUGS] Crash report for some ICU-52 (debian8) COLLATE and work_mem values) |