Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Peter Geoghegan <pg@bowt.ie>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Daniel Verite <daniel@manitou-mail.org>,
PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Date: 2017-08-07T15:55:21Z
Lists: pgsql-bugs, pgsql-hackers
On 8/7/17 11:17, Peter Eisentraut wrote: > On 8/6/17 17:17, Peter Geoghegan wrote: >> I wonder if it's worth considering distrusting ucol_strcollUTF8() on >> some ICU versions that prove to not be up to snuff. The function has >> only been around since ICU-50, released in late 2012. We could have >> something like a TRUST_UCOL_STRCOLLUTF8 override for >> HAVE_UCOL_STRCOLLUTF8. This might make sense as a compromise between >> not supporting somewhat older ICU versions and doing nothing at all. > > I can confirm that that avoids the crash in ICU 52, so it's something to > consider. We would need more testing about which other ICU versions are > affected, however. In my testing, there are no crashes in ICU 51 and ICU 53, so we could restrict this workaround to version 52 specifically. Perhaps someone else can confirm my test results. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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