diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2009-11-03 08:12:46 +0000 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2009-11-03 08:12:46 +0000 |
| commit | 1ef3f3cde3d2c5ff233209be01f58825a84348ab (patch) | |
| tree | fc24b3b8ca90751e6eef5c6cb756e8ebc64a6969 /src/backend/executor/nodeBitmapAnd.c | |
| parent | 3a2e45720429cc4328ba1956478ac3d5140bf282 (diff) | |
| download | postgresql-1ef3f3cde3d2c5ff233209be01f58825a84348ab.tar.gz postgresql-1ef3f3cde3d2c5ff233209be01f58825a84348ab.zip | |
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/nodeBitmapAnd.c')
0 files changed, 0 insertions, 0 deletions