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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paesold <mpaesold(at)gmx(dot)at>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)
Date: 2006-01-08 19:41:20
Message-ID: 43C16AE0.2080605@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

>Andrew Dunstan <andrew(at)dunslane(dot)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, "").)
>
>
>
>

All true, which is why I tried to avoid this solution.

However, I have not found another one that works. Specifically,
unsetting LANG and LC_COLLATE did not work as I thought it would.

If anyone can provide a better solution I will be very happy.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-01-08 19:47:23 Re: stat /etc/localtime 38000 times on startup?
Previous Message Tom Lane 2006-01-08 19:00:39 Re: catalog corruption bug