Обсуждение: 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_3_STABLE

Modified Files:
--------------
    pgsql/src/backend/libpq:
        pqformat.c (r1.47 -> r1.47.2.1)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/pqformat.c?r1=1.47&r2=1.47.2.1)
    pgsql/src/backend/utils/error:
        elog.c (r1.201.2.2 -> r1.201.2.3)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/error/elog.c?r1=1.201.2.2&r2=1.201.2.3)
    pgsql/src/backend/utils/mb:
        wchar.c (r1.66.2.2 -> r1.66.2.3)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/mb/wchar.c?r1=1.66.2.2&r2=1.66.2.3)
    pgsql/src/include/libpq:
        pqformat.h (r1.26 -> r1.26.2.1)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/libpq/pqformat.h?r1=1.26&r2=1.26.2.1)