Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)
Date: 2005-12-28 17:33:33
Message-ID: 45365.68.143.134.146.1135791213.squirrel@www.dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane said:
> "Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
>> It should certainly be fixed, but surely at best this would only delay
>> seeing the ugly locale effect - as soon as you call a perl function
>> you'll be back in the same boat regardless.
>
> Right, I was not suggesting that fixing the validator would avoid the
> bug. It just surprised me that libperl was getting called in the
> restore-a-dump scenario.
>
> BTW, I was just about to go change the validator, but if you want to do
> it go ahead...
>

no, please do.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruno Wolff III 2005-12-28 19:28:20 Re: Fixing row comparison semantics
Previous Message Andrew Dunstan 2005-12-28 17:23:59 Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)