From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <andreas+pg(at)gate450(dot)dyndns(dot)org>, <masm(at)fciencias(dot)unam(dot)mx>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: localization problem (and solution) |
Date: | 2005-12-29 03:03:43 |
Message-ID: | 3818.24.211.165.134.1135825423.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:
>> We have a build failure to fix first:
>>
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=loris&dt=2005-12-29%2000:44:52>
> Weird. It seems to be choking on linking to check_function_bodies, but
> plpgsql does that exactly the same way, and there's no problem there.
> I wonder whether all those warnings in the perl header files mean
> anything ...
We always get those - see
http://www.pgbuildfarm.org/cgi-bin/show_stage_log.pl?nm=loris&dt=2005-12-23%2019%3A56%3A12&stg=makefor example. One day when I get time I want to clean them up.
>
>> The issue is that if I set my machine's locale to Turkish or French,
>> say, it doesn't matter what locale I set during initdb or in
>> postgresql.conf, the server's log messages always seem to come out in
>> the machine's locale.
>
> Is this possibly related to the fact that we don't even try to do
> setlocale() for LC_MESSAGES
We can't on Windows - it doesn't define LC_MESSAGES. But libintl does some
stuff, I believe.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2005-12-29 03:05:30 | Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and |
Previous Message | Tom Lane | 2005-12-29 02:12:52 | Re: localization problem (and solution) |