diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2004-11-16 18:10:16 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2004-11-16 18:10:16 +0000 |
| commit | 7efa8411cc56383a9b7ac2203f310d0db81f0580 (patch) | |
| tree | a205f416cfee9d6c54864d06c72a2aa6f686f9e6 /src/backend/executor/nodeFunctionscan.c | |
| parent | 2bb3bcfcf9edb57d7bd3635b2201688defee6676 (diff) | |
Rethink plpgsql's way of handling SPI execution during an exception block.
We don't really want to start a new SPI connection, just keep using the old
one; otherwise we have memory management problems as illustrated by
John Kennedy's bug report of today. This requires a bit of a hack to
ensure the SPI stack state is properly restored, but then again what we
were doing before was a hack too, strictly speaking. Add a regression
test to cover this case.
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions