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.
Showing
- src/backend/libpq/pqformat.c 31 additions, 2 deletionssrc/backend/libpq/pqformat.c
- src/backend/utils/error/elog.c 62 additions, 33 deletionssrc/backend/utils/error/elog.c
- src/backend/utils/mb/wchar.c 7 additions, 20 deletionssrc/backend/utils/mb/wchar.c
- src/include/libpq/pqformat.h 2 additions, 1 deletionsrc/include/libpq/pqformat.h
Please register or sign in to comment