| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:51:48 |
| Message-ID: | CAH2-Wz==SYzY46YQH31Er0PJkbta0QoQq7N+wByfmYr9GXDxGA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Mon, Aug 7, 2017 at 10:39 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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?
I had it right the first time, actually -- it is possible.
There is a lack of any example of it in the docs. And, references to
CREATE COLLATION right under "23.2.2.2.2. ICU collations" in the docs
are under the title "Copying Collations". That threw me off.
I think that we are entitled to assume plenty about what collations
ICU makes available, at least per version.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2017-08-07 18:05:54 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
| Previous Message | Tom Lane | 2017-08-07 17:51:39 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-08-07 17:51:52 | Re: [GSOC][weekly report 9] Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions |
| Previous Message | Tom Lane | 2017-08-07 17:51:39 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |