]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 4a836ba) | 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:18 +0000 (16:56 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 26 Dec 2006 16:56:18 +0000 (16:56 +0000)
commitfccf99f0c81ac2ad9af6e6fa746375c39ca7ab0b
tree733c7b818d1d0a74c6cebe6e7b77a18985b26188tree | snapshot
parent4a836bad3abef2ca06ab77fac3de1357c097c3c2commit | 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.