When we are in error recursion trouble, arrange to suppress translation and
authorTom Lane <tgl@sss.pgh.pa.us>
Mon, 2 Mar 2009 21:19:14 +0000 (21:19 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Mon, 2 Mar 2009 21:19:14 +0000 (21:19 +0000)
commit39f691651f75c7b3004149b62bcd811c6f7080ca
tree48f6860b5d5abdd9655d3a121307ce265b9679e0
parent17b5cc3dbcdad7f088647e9baf8732c58fdda12b
When we are in error recursion trouble, arrange to suppress translation and
encoding conversion of any elog/ereport message being sent to the frontend.
This generalizes a patch that I put in last October, which suppressed
translation of only specific messages known to be associated with recursive
can't-translate-the-message behavior.  As shown in bug #4680, we need a more
general answer in order to have some hope of coping with broken encoding
conversion setups.  This approach seems a good deal less klugy anyway.

Patch in all supported branches.
src/backend/libpq/pqformat.c
src/backend/utils/error/elog.c
src/backend/utils/mb/wchar.c
src/include/libpq/pqformat.h