From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, "Thomas H(dot)" <me(at)alternize(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #4186: set lc_messages does not work |
Date: | 2008-07-15 14:22:02 |
Message-ID: | 200807151422.m6FEM2v23013@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> > Thomas H. wrote:
> >> so at least that explains the "changed" behaviour. nevertheless,
> >> LC_MESSAGES seems to be defunct - with the "locale" folder present,
> >> pg always picks the os' language and ignores the lc_message value.
>
> > This looks like I can reproduce though, at least on cvs head. Did this
> > work for you in previous versions?
>
> Maybe we were using a different build of gettext in the previous
> releases, one that didn't look at the same info as the current code?
>
> Anyway the patch mentioned at the start of the thread
> http://archives.postgresql.org/pgsql-patches/2008-02/msg00038.php
> purports to fix this. It doesn't seem to have gotten reviewed
> though.
Agreed. Magnus, someone, can we get feedback on the patch at this URL?
http://archives.postgresql.org/pgsql-patches/2008-02/msg00038.php
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-07-15 14:45:53 | Re: Psql or test application hangs when interface is down for the DB server |
Previous Message | Tom Lane | 2008-07-15 14:14:59 | Re: BUG #4296: Server crashes by restoring database |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-07-15 14:22:33 | Re: Is there anyway to create a TupleDesc with uint32 attribute easily? |
Previous Message | Tom Lane | 2008-07-15 14:09:08 | Re: PATCH: CITEXT 2.0 v3 |