Re: BUG #4186: set lc_messages does not work - Mailing list pgsql-bugs

From Thomas H.
Subject Re: BUG #4186: set lc_messages does not work
Date
Msg-id 483E0153.3070200@alternize.com
Whole thread Raw
In response to Re: BUG #4186: set lc_messages does not work  ("Thomas H." <me@alternize.com>)
Responses Re: BUG #4186: set lc_messages does not work  ("Dave Page" <dpage@pgadmin.org>)
Re: BUG #4186: set lc_messages does not work  (Magnus Hagander <magnus@hagander.net>)
List pgsql-bugs
From: Thomas H. <me@alternize.com>
> what i noticed: if i delete the folder share/locale/de/ the system
> messages are back to english - but that can't be THE solution, can it? :)

well, it actually was the solution, at least to the weird part of the
problem:

there are two versions of win32 binaries available on postgres.org.
there's the installer msi version, and there is the installerless zip
version.

the installer version does NOT install the folder "share/locale/"! so
when using the msi installer, postgres has no translations at all - thus
the fallback to english.

the zipped version contains the "share/locale/" folder. for installing
8.3.0, i've been using the msi installer version. for upgrading to
8.3.1, i've been unpacking the files from zip version into the
postgresql directory...

i've just verified that the 8.3.1 msi version provided on postgres.org
also does NOT contain the "locale" folder & files. should i report this
as a separate bug/problem?

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.

- thomas

pgsql-bugs by date:

Previous
From: "Thomas H."
Date:
Subject: Re: BUG #4186: set lc_messages does not work
Next
From: "Jeferson Kasper"
Date:
Subject: BUG #4207: EXTRACT function