Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: prevent encoding conversion recursive error
Date
Msg-id 11566.1123555887@sss.pgh.pa.us
Whole thread Raw
In response to Re: prevent encoding conversion recursive error  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: prevent encoding conversion recursive error
List pgsql-patches
Tree view 
I wrote:
> This does not look real easy to fix.  Who's up for reimplementing
> gettext and a few other pieces from scratch?

However, I did find


http://gnu.miscellaneousmirror.org/software/libc/manual/html_node/Charset-conversion-in-gettext.html#Charset-conversion-in-gettext

which leads to the question "why aren't we using
bind_textdomain_codeset() to tell gettext what character set it should
produce"?

            regards, tom lane

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: prevent encoding conversion recursive error
Next
From: yuanjia lee
Date:
Subject: Allow WAL information to recover corrupted pg_controldata patch