pgsql: - During dblink_open, if transaction state was IDLE, force cursor

From: joe(at)postgresql(dot)org (Joe Conway)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: - During dblink_open, if transaction state was IDLE, force cursor
Date: 2006-06-21 16:43:11
Message-ID: 20060621164311.D942A9FA65C@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
- During dblink_open, if transaction state was IDLE, force cursor count to
initially be 0. This is needed as a previous ABORT might have wiped out
an automatically opened transaction without maintaining the cursor count.
- Fix regression test expected file for the correct ERROR message, which
we now get given the above bug fix.

Modified Files:
--------------
pgsql/contrib/dblink:
dblink.c (r1.55 -> r1.56)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/dblink/dblink.c.diff?r1=1.55&r2=1.56)
pgsql/contrib/dblink/expected:
dblink.out (r1.16 -> r1.17)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/dblink/expected/dblink.out.diff?r1=1.16&r2=1.17)

Browse pgsql-committers by date

  From Date Subject
Next Message Joe Conway 2006-06-21 16:43:46 pgsql: - During dblink_open, if transaction state was IDLE, force cursor
Previous Message Tom Lane 2006-06-21 16:05:11 pgsql: Clean up psql variable code a little: eliminate unnecessary tests