From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(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-09 18:09:36 |
Message-ID: | CAH2-Wz=tgsX7awuvCJMz9rHhHT=iy-+bMJBS6h_+7B4K7Bx+9g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Wed, Aug 9, 2017 at 11:07 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Yes, it is. I think that's fine, though. Other database systems that
>> use ICU for collations do this. Without exception, I think.
>
> Actually, I don't think that's the issue at all. People are free to
> make other ICU collations if they want to. My point is that we should
> encourage them to do that, rather than depend on initdb-provided
> collations, because manually-created collations are much more certain
> to move across version upgrades safely. If we were sure that
> pg_import_system_collations would produce pretty much the same set of
> collation names with future ICU releases as it does with current ones,
> then there would be no issue --- but the evidence at hand suggests the
> opposite. I want to do something to address that stability issue before
> it comes back to bite us.
I must have been unclear, then. I am fully in agreement with what you say here.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2017-08-09 18:46:18 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
Previous Message | Tom Lane | 2017-08-09 18:07:48 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2017-08-09 18:46:18 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
Previous Message | Tom Lane | 2017-08-09 18:07:48 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |