Peter Eisentraut wrote:
> Note that only glibc supports switching the language at run time. And
> doing it is probably very expensive if you want to do it twice per
> message.
Ouch :-(
> I think you could probably get much of the use case out of this if you
> concentrate on making two switches for the client and the log, which can
> be set to a language or "untranslated", and if you choose a language it
> has to be the same for both.
So we'd go with a single setting to define language, which would be the
current lc_messages, and two new settings, say translate_log_messages
and translate_client_messages, the latter being USERSET.
Does that sound reasonable?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
