| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| 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 02:12:52 |
| Message-ID: | 3093.1135822372@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 ...
> 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?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-12-29 03:03:43 | Re: localization problem (and solution) |
| Previous Message | Bruce Momjian | 2005-12-29 01:58:14 | Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and |