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

pgsql: Repair bug #2836: SPI_execute_plan returned zero if none of the

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Repair bug #2836: SPI_execute_plan returned zero if none of the
Date: 2006-12-26 16:56:22
Message-ID: 20061226165622.E7FE99FA217@postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Repair bug #2836: SPI_execute_plan returned zero if none of the querytrees
were marked canSetTag.  While it's certainly correct to return the result
of the last one that is marked canSetTag, it's less clear what to do when
none of them are.  Since plpgsql will complain if zero is returned, the
8.2.0 behavior isn't good.  I've fixed it to restore the prior behavior of
returning the physically last query's result code when there are no
canSetTag queries.

Tags:
----
REL8_2_STABLE

Modified Files:
--------------
    pgsql/src/backend/executor:
        spi.c (r1.165.2.1 -> r1.165.2.2)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/spi.c.diff?r1=1.165.2.1&r2=1.165.2.2)

pgsql-committers by date

Next:From: Tom LaneDate: 2006-12-26 19:26:46
Subject: pgsql: Repair bug #2839: the various ExecReScan functions need to reset
Previous:From: Tom LaneDate: 2006-12-26 16:56:18
Subject: pgsql: Repair bug #2836: SPI_execute_plan returned zero if none of the

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