Re: Getting server crash on Windows when using ICU collation

From: Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Getting server crash on Windows when using ICU collation
Date: 2017-06-23 05:14:54
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers


On Wed, Jun 21, 2017 at 9:50 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> On Wed, Jun 21, 2017 at 12:15 AM, Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>> On 6/20/17 09:23, Amit Kapila wrote:
>>> To avoid that why can't we use the same icu path for executing uconv
>>> as we are using for linking?
>> Yeah, you'd need to use prefix $self->{options}->{icu} . '\bin\uconv' or
>> something like that.
> That's what I had in mind as well.

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.

With Regards,
Ashutosh Sharma

Attachment Content-Type Size
detect_ICU_version_v4.patch application/octet-stream 1.7 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Yugo Nagata 2017-06-23 05:22:46 Re: Autovacuum launcher occurs error when cancelled by SIGINT
Previous Message amul sul 2017-06-23 04:42:48 Re: Multi column range partition table