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

From Tom Lane
Subject Re: prevent encoding conversion recursive error
Date
Msg-id 3944.1124056094@sss.pgh.pa.us
Whole thread Raw
In response to Re: prevent encoding conversion recursive error  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: prevent encoding conversion recursive error  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-patches
Peter Eisentraut <peter_e@gmx.net> writes:
> Am Dienstag, 9. August 2005 04:51 schrieb Tom Lane:
>> which leads to the question "why aren't we using
>> bind_textdomain_codeset() to tell gettext what character set it should
>> produce"?

> That would probably require us to solve the question on how to translate
> PostgreSQL encoding names to OS encoding names.

Yeah, but don't we already have some code for that (or, actually, the
reverse direction) in initdb?  It's probably not perfect, but it'd be
a lot better than crashing.

            regards, tom lane

pgsql-patches by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: prevent encoding conversion recursive error
Next
From: Peter Eisentraut
Date:
Subject: Re: prevent encoding conversion recursive error