pgsql: Fix a couple of contrib/dblink bugs.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix a couple of contrib/dblink bugs.
Date: 2012-04-04 00:44:15
Message-ID: E1SFEKd-0002eg-4A@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix a couple of contrib/dblink bugs.

dblink_exec leaked temporary database connections if any error occurred
after connection setup, for example
SELECT dblink_exec('...connect string...', 'select 1/0');
Add a PG_TRY block to ensure PQfinish gets done when it is needed.
(dblink_record_internal is on the hairy edge of needing similar treatment,
but seems not to be actively broken at the moment.)

Also, in 9.0 and up, only one of the three functions using tuplestore
return mode was properly checking that the query context would allow
a tuplestore result.

Noted while reviewing dblink patch. Back-patch to all supported branches.

Branch
------
REL9_1_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/8d2a5fb219aab954fe6642a2c1abdaa058ddeaef

Modified Files
--------------
contrib/dblink/dblink.c | 204 ++++++++++++++++++++++++++--------------------
1 files changed, 115 insertions(+), 89 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2012-04-04 19:06:32 pgsql: Fix syslogger to not lose log coherency under high load.
Previous Message Robert Haas 2012-04-03 12:39:29 pgsql: Arrange for on_exit_nicely to be thread-safe.