From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Greg Sabino Mullane <greg(at)turnstep(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Finding last checkpoint time |
Date: | 2010-07-23 22:01:11 |
Message-ID: | 1279922236-sup-6178@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Excerpts from Greg Sabino Mullane's message of vie jul 23 19:08:27 UTC 2010:
>
> Hash: RIPEMD160
>
> > Hmm, wouldn't have it been easier to set LC_MESSAGES to C before
> > calling pg_controldata?
>
> To be honest, I can't remember why that wasn't working for me when
> I tried it some time ago. I just verified that it *will* work,
> however, when I set LANGUAGE (LC_MESSAGES has no effect).
Hmm, now that you mention it, I think I remember different systems
honoring different env vars. To be safe you probably want to set the
lot of them -- LANGUAGE, LANG, LC_ALL.
Note that LC_MESSAGES has no effect if LC_ALL is set. I think other
vars also override LC_MESSAGES in some systems.
Still, this is way better than a collection of translated strings;
consider a translator fixing a typo, or choosing a different wording, or
a new language being added.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael A. Peters | 2010-07-23 22:20:20 | pg_dump, shemas, backup strategy |
Previous Message | Daniel Verite | 2010-07-23 21:53:13 | Re: prepared statements |