From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 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-14 17:22:09 |
Message-ID: | 5261d23c-1864-bec9-538c-24f25c7629cc@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On 8/9/17 17:29, Peter Geoghegan wrote:
> On Wed, Aug 9, 2017 at 2:26 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Peter Geoghegan <pg(at)bowt(dot)ie> writes:
>>> It would help if CREATE COLLATION left new
>>> ICU collations with the same useful "Description" as initdb created
>>> collations will have; maybe that should be added.
I had been thinking about that, too, while I was writing it, but there
is the semantic objection:
>> I do not think it is CREATE COLLATION's job to provide a comment;
>> no other CREATE command does so.
How about a special option in the CREATE COLLATION to create the comment
automatically on demand? Sample patch attached.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
0001-Add-CREATE-COLLATION-auto_comment-option.patch | text/plain | 2.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2017-08-14 17:41:24 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
Previous Message | Peter Geoghegan | 2017-08-14 16:51:34 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-08-14 17:26:39 | Re: shared memory based stat collector (was: Sharing record typmods between backends) |
Previous Message | Mengxing Liu | 2017-08-14 17:21:38 | Re: [GSOC][weekly report 9] Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions |