Re: prevent encoding conversion recursive error - Mailing list pgsql-patches

From Tom Lane
Subject Re: prevent encoding conversion recursive error
Date
Msg-id 17347.1124581729@sss.pgh.pa.us
Whole thread Raw
In response to Re: prevent encoding conversion recursive error  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: prevent encoding conversion recursive error  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-patches
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Is there a TODO here?

Yeah:

* Fix problems with wrong runtime encoding conversion for NLS message files

One thing that occurred to me is that we might be able to simplify the
problem by adopting a project standard that all NLS message files shall
be in UTF8, period.  Then we only have one encoding name to figure out
rather than N.  Maybe this doesn't help much ...

            regards, tom lane

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: A couple of patches for PostgreSQL 64bit support
Next
From: Tom Lane
Date:
Subject: Re: PL/Perl embedding string common elements