Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Peter Geoghegan <pg@bowt.ie>, Daniel Verite <daniel@manitou-mail.org>,
PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Date: 2017-08-07T17:51:39Z
Lists: pgsql-bugs, pgsql-hackers
I wrote: > I'm on board with Peter G's proposal: let's distrust ucol_strcollUTF8 > in ICU < 53. If those folk felt a need to rewrite it completely after > only three release cycles, that should tell us something. A bit of googling turned up this document: http://site.icu-project.org/design/collation/v2 which indicates that the ucol_strcollUTF8 rewrite was really just one facet of a rather major reimplementation. But still, that document says specifically that they knew of multiple bugs and suspected many more. 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. 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. regards, tom lane
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