Re: client_lc_messages

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: client_lc_messages
Date: 2009-10-23 15:28:23
Message-ID: 20091023152823.GB355@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2009-10-23 15:46:37 Re: plpgsql EXECUTE will not set FOUND
Previous Message Kevin Grittner 2009-10-23 15:15:05 Re: Using views for row-level access control is leaky