When we are in error recursion trouble, arrange to suppress translation and
authorTom Lane <[email protected]>
Mon, 2 Mar 2009 21:19:23 +0000 (21:19 +0000)
committerTom Lane <[email protected]>
Mon, 2 Mar 2009 21:19:23 +0000 (21:19 +0000)
commitcb35ebab1a2a49c5ec8344455620d5b0981f2fe3
tree749face15eacff91f102dfee50b73cf2c2805eb9
parentc811ba18eaaddaccf491f4e543f177ea4cf79591
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