pgsql: When we are in error recursion trouble, arrange to suppress

Log Message:
-----------
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.

Tags:
----
REL8_1_STABLE

Modified Files:
--------------
pgsql/src/backend/libpq:
pqformat.c (r1.40 -> r1.40.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/pqformat.c?r1=1.40&r2=1.40.2.1)
pgsql/src/backend/utils/error:
elog.c (r1.167.2.7 -> r1.167.2.8)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/error/elog.c?r1=1.167.2.7&r2=1.167.2.8)
pgsql/src/backend/utils/mb:
wchar.c (r1.47.2.8 -> r1.47.2.9)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/mb/wchar.c?r1=1.47.2.8&r2=1.47.2.9)
pgsql/src/include/libpq:
pqformat.h (r1.23 -> r1.23.6.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/libpq/pqformat.h?r1=1.23&r2=1.23.6.1)