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: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
Daniel Verite <daniel@manitou-mail.org>, PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Date: 2017-08-09T21:29:09Z
Lists: pgsql-bugs, pgsql-hackers
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 do not think it is CREATE COLLATION's job to provide a comment; > no other CREATE command does so. It's not a comment. It's a description that comes from ICU. Just like when collations are added by initdb, so that there is some kind of parity. The user doesn't get a say in what it is. It helps the user to verify that they're getting what they thought they were, which seems very valuable, given how loosely the 'locale' string they provide may be interpreted. -- 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