]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 5ceb508) | patch
Repair bug #2836: SPI_execute_plan returned zero if none of the querytrees
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 26 Dec 2006 16:56:22 +0000 (16:56 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 26 Dec 2006 16:56:22 +0000 (16:56 +0000)
commitb85a4cda83bc7a19031730465d358e415935f05b
treef4f24fd89828588f5d24cde949909a1bb0ec4a05tree | snapshot
parent5ceb50842286c101c94b1077f3e8b068278ebc07commit | diff
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.
src/backend/executor/spi.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.