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-07T18:05:54Z
Lists: pgsql-bugs, pgsql-hackers
On Mon, Aug 7, 2017 at 10:51 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > At this point I'm thinking that really what we ought to do is deprecate > using any pre-53 ICU release for Postgres. It is very clear that those > versions are an entirely different beast from 53-and-up, and that they > are now abandonware so far as ICU upstream is concerned. +1. I think that ICU is very important, and I would like to see it become the defacto standard collation provider, but I don't think it's something that needs to happen on an aggressive schedule. > I have not checked, but I wonder whether 53 is also when the large > change in the set of available collations happened. Maybe rejecting > pre-53 would also be enough to assuage my concerns about disappearing > collations. I bet it would. Although, I should point out that ICU has an annoying habit of being very tolerant of misspellings, or alternative spellings, so it might not be as bad as it appeared. We could perhaps fix this by taking a greater interest in the collations that are initially available, documenting useful variations, and so on. We should do that anyway. -- 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