diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2006-12-26 16:56:18 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2006-12-26 16:56:18 +0000 |
| commit | fccf99f0c81ac2ad9af6e6fa746375c39ca7ab0b (patch) | |
| tree | 733c7b818d1d0a74c6cebe6e7b77a18985b26188 /src/backend/executor/nodeValuesscan.c | |
| parent | 4a836bad3abef2ca06ab77fac3de1357c097c3c2 (diff) | |
| download | postgresql-fccf99f0c81ac2ad9af6e6fa746375c39ca7ab0b.tar.gz postgresql-fccf99f0c81ac2ad9af6e6fa746375c39ca7ab0b.zip | |
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.
Diffstat (limited to 'src/backend/executor/nodeValuesscan.c')
0 files changed, 0 insertions, 0 deletions