pgsql: When an ERROR happens on a dblink remote connection, take pains

From: joe(at)postgresql(dot)org (Joe Conway)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: When an ERROR happens on a dblink remote connection, take pains
Date: 2008-07-03 03:56:57
Message-ID: [email protected]
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
When an ERROR happens on a dblink remote connection, take
pains to pass the ERROR message components locally, including
using the passed SQLSTATE. Also wrap the passed info in an
appropriate CONTEXT message. Addresses complaint by Henry
Combrinck. Joe Conway, with much good advice from Tom Lane.

Modified Files:
--------------
pgsql/contrib/dblink:
dblink.c (r1.73 -> r1.74)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/dblink/dblink.c?r1=1.73&r2=1.74)
pgsql/contrib/dblink/expected:
dblink.out (r1.23 -> r1.24)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/dblink/expected/dblink.out?r1=1.23&r2=1.24)

Browse pgsql-committers by date

  From Date Subject
Next Message User C2main 2008-07-03 10:02:43 muninpgplugins - muninpgplugins: correct install.sh to output symlinks
Previous Message Tom Lane 2008-07-03 03:37:17 pgsql: Fix psql's \d and allied commands to work with all server