Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Daniel Verite <daniel(at)manitou-mail(dot)org>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values
Date: 2017-08-07 15:17:20
Message-ID: 686574df-66c0-600f-6c62-3f2560ce92a3@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

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.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2017-08-07 15:55:21 Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values
Previous Message Peter Eisentraut 2017-08-07 14:54:13 Re: BUG #14769: Logical replication error "cache lookup failed for type 0"

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2017-08-07 15:55:21 Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values
Previous Message Fabrízio de Royes Mello 2017-08-07 15:14:52 Re: Patch: Add --no-comments to skip COMMENTs with pg_dump