Re: client_lc_messages - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: client_lc_messages
Date
Msg-id 9837222c0910221659l152513e0vf6b46111980f7100@mail.gmail.com
Whole thread Raw
In response to client_lc_messages  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: client_lc_messages
List pgsql-hackers
2009/10/22 Alvaro Herrera <alvherre@commandprompt.com>:
> So right now we have a single GUC determining the language that log
> messages are in, and it is PGC_SUSET to avoid a user from sending
> messages to the log that the DBA cannot read.
>
> However, this means that the client cannot get the messages in the
> language of his choice.
>
> What I am wondering right now is whether we could have two separate
> attributes, one SUSET defining what goes to the log, and another one
> USERSET defining what's sent to the client.
>
> This would require a bit of shuffling, because right now we translate
> the message pretty early in the call chain -- way before we try to send
> it to client or server.  This would need to be postponed, or
> alternatively, we would need to store a second, untranslated copy so
> that another translation can take place later, if necessary.
>
> Thoughts?

This would allow me to have the client messages in one language and
the log in English, right? If so, +100 or sometihng like that, if it's
not too hard to do. Meaning it's not just encoding, but actual
translation?

-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: table corrupted
Next
From: Alvaro Herrera
Date:
Subject: Re: client_lc_messages