Re: NLS vs error processing, again (was Re: Composite Type with Domain) - Mailing list pgsql-bugs

From Tom Lane
Subject Re: NLS vs error processing, again (was Re: Composite Type with Domain)
Date
Msg-id 23106.1144205063@sss.pgh.pa.us
Whole thread Raw
In response to Re: NLS vs error processing, again (was Re: Composite Type  (Euler Taveira de Oliveira <euler@timbira.com>)
List pgsql-bugs
Euler Taveira de Oliveira <euler@timbira.com> writes:
> Tom Lane wrote:
>> It seems to me that there basically is no graceful solution to this sort
>> of mismatch.  It might be possible to kluge things so that we disable
>> NLS once we've recursed too many times in error processing, but that's
>> surely pretty ugly.  What would be a lot more user-friendly would be to
>> refuse the attempt to set client_encoding to something that can't handle
>> our error message encoding, but I don't know what a reasonable set of
>> restrictions would be.

> Maybe it's the time to convert all PO files to UTF-8. I'm in process to
> convert pt_BR ones.

What does that have to do with it?

            regards, tom lane

pgsql-bugs by date:

Previous
From: Euler Taveira de Oliveira
Date:
Subject: Re: NLS vs error processing, again (was Re: Composite Type
Next
From: Tom Lane
Date:
Subject: Re: NLS vs error processing, again