Re: localization problem (and solution) - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: localization problem (and solution)
Date
Msg-id 34077.68.143.134.146.1135181280.squirrel@www.dunslane.net
Whole thread Raw
In response to Re: localization problem (and solution)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: localization problem (and solution)  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: localization problem (and solution)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane said:
> Andreas Seltenreich <andreas+pg@gate450.dyndns.org> writes:
>> I'm afraid having LC_ALL in the environment at this time would still
>> do the wrong thing on setlocale(LC_ALL, ""); since a LC_ALL
>> environment variable overrides the other categories.
>
> Doh, of course, I was misremembering the precedence.  So we need
>     LANG=C
>     LC_ALL unset (probably LANGUAGE too, for glibc)
>     others as stated
>


We need to test any solution carefully on Windows, which deals with locales
very differently from *nix, and where we still have some known locale issues
(see recent discussion).

I wonder if the complained of behaviour is triggered by our recent changes
to support utf8 in pl/perl?

cheers

andrew




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: localization problem (and solution)
Next
From: Tom Lane
Date:
Subject: Better path-matching for package relocatability (was Re: [BUGS] horology regression test failure)