From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Getting server crash on Windows when using ICU collation |
Date: | 2017-08-11 02:29:42 |
Message-ID: | 7861fd82-396d-d673-487d-30a00d48b226@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/10/17 22:21, Peter Geoghegan wrote:
> On Thu, Aug 10, 2017 at 3:57 PM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>> On Thu, Aug 10, 2017 at 11:02 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>> On Fri, Jun 23, 2017 at 1:14 AM, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> wrote:
>>>> Okay, attached is the patch which first detects the platform type and
>>>> runs the uconv commands accordingly from the corresponding icu bin
>>>> path. Please have a look and let me know for any issues. Thanks.
>>>
>>> Should this be on the open items list?
>>
>> Maybe. Peter E has a patch to fix the other issue (ICU 52 has a buggy
>> ucol_strcollUTF8()) by never using it on ICU versions prior to 53. He
>> posted this just yesterday.
>
> He committed it just now, so that's the end of this Windows issue, I suppose.
Yes, I think so.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-08-11 02:31:01 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
Previous Message | Peter Geoghegan | 2017-08-11 02:21:57 | Re: Getting server crash on Windows when using ICU collation |