Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug) - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)
Date
Msg-id 43C2F652.3030901@dunslane.net
Whole thread Raw
In response to Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
It has probably been sufficiently mitigated on *nix. On Windows, the 
choice seems to be between living with the risk and trying my "put the 
locales back where they were" patch, which as Tom and Greg point out 
might have other consequences. Take your pick.

cheers

andrew

Bruce Momjian wrote:

>Is there a TODO here, even if the Perl folks are supposed to fix it?
>
>---------------------------------------------------------------------------
>
>Andrew Dunstan wrote:
>  
>
>>Tom Lane wrote:
>>
>>    
>>
>>>>I'm just about out of ideas and right out of time to spend on this.
>>>>   
>>>>
>>>>        
>>>>
>>>We could just file a Perl bug report and wait for them to fix it.
>>>
>>>    
>>> 
>>>
>>>      
>>>
>>done
>>
>>    
>>
>


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)
Next
From: Bruce Momjian
Date:
Subject: Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)