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

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:46
Message-ID: 20060621164346.3FA8B9FB1BC@postgresql.org (view raw or flat)
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.

Tags:
----
REL8_1_STABLE

Modified Files:
--------------
    pgsql/contrib/dblink:
        dblink.c (r1.48.2.2 -> r1.48.2.3)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/dblink/dblink.c.diff?r1=1.48.2.2&r2=1.48.2.3)
    pgsql/contrib/dblink/expected:
        dblink.out (r1.16 -> r1.16.2.1)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/dblink/expected/dblink.out.diff?r1=1.16&r2=1.16.2.1)

pgsql-committers by date

Next:From: Tom LaneDate: 2006-06-21 18:09:53
Subject: pgsql: Eliminate a gratuitously different wording of the 'cannot use
Previous:From: Joe ConwayDate: 2006-06-21 16:43:11
Subject: pgsql: - During dblink_open, if transaction state was IDLE, force cursor

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