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: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Daniel Verite <daniel@manitou-mail.org>, PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Date: 2017-08-07T17:34:22Z
Lists: pgsql-bugs, pgsql-hackers
On Mon, Aug 7, 2017 at 10:30 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > So they added emojis (I'm with Peter G that we could do without installing > that by default) ... but what became of the af-NA and af-ZA collations? > If I were a user who'd adopted one of those as a database collation, > I'd be seriously unhappy to have them go away in a later PG release. > > I think we'd be well advised to filter the set of installed-by-default > collations rather strongly, in hope of avoiding such problems. For > starters, do we really need the keyword variants at all? People who > know what those are for can create their own collations, and take > their own risks of the feature disappearing in later ICU releases. 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. -- 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