| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | 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-07 17:39:26 |
| Message-ID: | 32710.1502127566@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> On Mon, Aug 7, 2017 at 10:30 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I think we'd be well advised to filter the set of installed-by-default
>> collations rather strongly, in hope of avoiding such problems. For
>> starters, do we really need the keyword variants at all? People who
>> know what those are for can create their own collations, and take
>> their own risks of the feature disappearing in later ICU releases.
> Actually, I think I was wrong about it being possible to create the
> collations after the fact. CREATE COLLATION simply doesn't support
> that. This surprised me.
Surely that's a bug?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Verite | 2017-08-07 17:39:38 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
| Previous Message | Peter Geoghegan | 2017-08-07 17:34:22 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Verite | 2017-08-07 17:39:38 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
| Previous Message | Peter Geoghegan | 2017-08-07 17:34:22 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |