Re: NLS vs error processing, again (was Re: Composite Type

From: Euler Taveira de Oliveira <euler(at)timbira(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: JiangWei <jw(dot)pgsql(at)sduept(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: NLS vs error processing, again (was Re: Composite Type
Date: 2006-04-05 02:10:35
Message-ID: 4433271B.5090204@timbira.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

--
Euler Taveira de Oliveira

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Wang Haiyong 2006-04-05 02:34:17 Bug in window xp
Previous Message Tom Lane 2006-04-04 19:45:32 Re: BUG #2375: ALTER COLUMN TYPE on composite types