Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE andwork_mem values
От | Peter Geoghegan |
---|---|
Тема | Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE andwork_mem values |
Дата | |
Msg-id | CAH2-WzkHUMDfagwqVFSepv7dJqrghpG39+LtJiENu9SKRAcuNg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE andwork_mem values (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>) |
Ответы |
Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE and work_mem values
|
Список | pgsql-bugs |
On Mon, Aug 14, 2017 at 10:22 AM, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote: > On 8/9/17 17:29, Peter Geoghegan wrote: >> On Wed, Aug 9, 2017 at 2:26 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>> Peter Geoghegan <pg@bowt.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. I must admit that I missed that the description was cataloged as a comment. Is it out of the question to add another column to pg_collation, that just always has the ICU-provided description? These seem like separate concerns to me. -- Peter Geoghegan -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
В списке pgsql-bugs по дате отправления: