]> granicus.if.org Git - postgresql/commit
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:23 +0000 (21:19 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Mon, 2 Mar 2009 21:19:23 +0000 (21:19 +0000)
commit1f3832b5d2728e5d4333324dbbb1ecd4634ded14
tree85863ddee8d0d3150cfb61a8d679c44e0d4e23ca
parent5156266ab65d67b92493663435051a8bf36ae47d
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