| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
| 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 with Domain) |
| Date: | 2006-04-05 02:44:23 |
| Message-ID: | 23106.1144205063@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Euler Taveira de Oliveira <euler(at)timbira(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2006-04-05 03:20:47 | Re: NLS vs error processing, again |
| Previous Message | Wang Haiyong | 2006-04-05 02:34:17 | Bug in window xp |