pgsql: Bring some order and sanity to error handling in the xml patch. - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Bring some order and sanity to error handling in the xml patch.
Date
Msg-id 20061224182559.5F76B9FA294@postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Bring some order and sanity to error handling in the xml patch.
Use a TRY block instead of (inadequate) ad-hoc coding to ensure that
libxml is cleaned up after a failure.  Report the intended SQLCODE
instead of defaulting to XX000.  Avoid risking use of a dangling
pointer by keeping the persistent error buffer in TopMemoryContext.
Be less trusting that error messages don't contain %.

This patch doesn't do anything about changing the way the messages
are put together --- this is just about mechanism.

Modified Files:
--------------
    pgsql/src/backend/utils/adt:
        xml.c (r1.4 -> r1.5)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/xml.c.diff?r1=1.4&r2=1.5)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix machine-dependent crash in sqlchar_to_unicode().
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Make HISTCONTROL=ignoredups work again (broken by misordering of