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

From Tom Lane
Subject Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)
Date
Msg-id 25808.1136745847@sss.pgh.pa.us
Whole thread Raw
In response to Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)  (Andrew Dunstan <andrew@dunslane.net>)
Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> The attached patch against cvs tip does seem to work. Instead of playing 
> with the environment, we simply allow perl to do its worst and then put 
> things back the way we wanted them.

Doesn't that screw up Perl, though?  Its idea of what the locale is
will be wrong.

Maybe that's the least bad alternative available, but it doesn't seem
like we're there yet.

(Of course, the *big* problem with this approach is that it's
Perl-specific, and won't do a thing for any other libraries that
might try to do setlocale(LC_ALL, "").)
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Luke Lonergan"
Date:
Subject: Re: Libpq COPY optimization
Next
From: Tom Lane
Date:
Subject: Re: catalog corruption bug