Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, Daniel Verite <daniel@manitou-mail.org>, PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Date: 2017-08-14T17:41:24Z
Lists: pgsql-bugs, pgsql-hackers
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
Commits
-
Reject use of ucol_strcollUTF8() before ICU 53
- d6391b03b302 10.0 landed
-
Rethink behavior of pg_import_system_collations().
- 0b13b2a7712b 10.0 cited
-
Faster expression evaluation and targetlist projection.
- b8d7f053c5c2 10.0 cited