Skip site navigation (1) Skip section navigation (2)

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

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: When we are in error recursion trouble, arrange to suppress
Date: 2009-03-02 21:19:14
Message-ID: 20090302211914.19A6B755AA5@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
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_0_STABLE

Modified Files:
--------------
    pgsql/src/backend/libpq:
        pqformat.c (r1.37 -> r1.37.4.1)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/pqformat.c?r1=1.37&r2=1.37.4.1)
    pgsql/src/backend/utils/error:
        elog.c (r1.155.4.9 -> r1.155.4.10)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/error/elog.c?r1=1.155.4.9&r2=1.155.4.10)
    pgsql/src/backend/utils/mb:
        wchar.c (r1.40.4.6 -> r1.40.4.7)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/mb/wchar.c?r1=1.40.4.6&r2=1.40.4.7)
    pgsql/src/include/libpq:
        pqformat.h (r1.23 -> r1.23.4.1)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/libpq/pqformat.h?r1=1.23&r2=1.23.4.1)

pgsql-committers by date

Next:From: Tom LaneDate: 2009-03-02 21:19:23
Subject: pgsql: When we are in error recursion trouble, arrange to suppress
Previous:From: Tom LaneDate: 2009-03-02 21:19:05
Subject: pgsql: When we are in error recursion trouble, arrange to suppress

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group