pgsql: Repair bug #2836: SPI_execute_plan returned zero if none of the - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Repair bug #2836: SPI_execute_plan returned zero if none of the
Date
Msg-id 20061226165622.E7FE99FA217@postgresql.org
Whole thread Raw
List 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:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Repair bug #2836: SPI_execute_plan returned zero if none of the
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Repair bug #2839: the various ExecReScan functions need to reset