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:18
Message-ID: 20061226165618.85BE09FA182@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
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.

Modified Files:
--------------
pgsql/src/backend/executor:
spi.c (r1.166 -> r1.167)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/spi.c.diff?r1=1.166&r2=1.167)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2006-12-26 16:56:22 pgsql: Repair bug #2836: SPI_execute_plan returned zero if none of the
Previous Message Tom Lane 2006-12-26 16:14:58 pgsql: Remove incorrect semicolon in example.