summaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeFunctionscan.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2009-11-03 08:44:52 +0000
committerPeter Eisentraut <peter_e@gmx.net>2009-11-03 08:44:52 +0000
commit9250485846a924e5ccfc21c37132a0f16e8210b1 (patch)
treea24ef2bd058b2123a9c2fa761198dd7433be771e /src/backend/executor/nodeFunctionscan.c
parent2a47208a9356b0656446d841d61ff78b34750391 (diff)
Fix obscure segfault condition in PL/Python
In PLy_output(), when the elog() call in the TRY branch throws an exception (this can happen when a statement timeout kicks in, for example), the PyErr_SetString() call in the CATCH branch can cause a segfault, because the Py_XDECREF(so) call before it releases memory that is still used by the sv variable that PyErr_SetString() uses as argument, because sv points into memory owned by so. Backpatched back to 8.0, where this code was introduced. I also threw in a couple of volatile declarations for variables that are used before and after the TRY. I don't think they caused the crash that I observed, but they could become issues.
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions