aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistscan.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2009-11-03 08:29:51 +0000
committerPeter Eisentraut <peter_e@gmx.net>2009-11-03 08:29:51 +0000
commitdb925b1a3c4172707c21956c9b27c28fce086e02 (patch)
treed5ebd581219a8f157680fe2a46d2f877ba478174 /src/backend/access/gist/gistscan.c
parent3753017a2005b4df03ec5bf9f51be651a1f796ad (diff)
downloadpostgresql-db925b1a3c4172707c21956c9b27c28fce086e02.tar.gz
postgresql-db925b1a3c4172707c21956c9b27c28fce086e02.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/access/gist/gistscan.c')
0 files changed, 0 insertions, 0 deletions