aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-03-26 16:41:38 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2014-03-26 16:41:38 -0400
commit6b3b15e5348593d882ce12c76720daec7c22e7e9 (patch)
tree5fed5d828f6d2ca873508029b2de4c64914a35dc /src/backend/access/gist
parent6fe8411ffb7119010b80b34044dccd4614bda175 (diff)
downloadpostgresql-6b3b15e5348593d882ce12c76720daec7c22e7e9.tar.gz
postgresql-6b3b15e5348593d882ce12c76720daec7c22e7e9.zip
Fix refcounting bug in PLy_modify_tuple().
We must increment the refcount on "plntup" as soon as we have the reference, not sometime later. Otherwise, if an error is thrown in between, the Py_XDECREF(plntup) call in the PG_CATCH block removes a refcount we didn't add, allowing the object to be freed even though it's still part of the plpython function's parsetree. This appears to be the cause of crashes seen on buildfarm member prairiedog. It's a bit surprising that we've not seen it fail repeatably before, considering that the regression tests have been exercising the faulty code path since 2009. The real-world impact is probably minimal, since it's unlikely anyone would be provoking the "TD["new"] is not a dictionary" error in production, and that's the only case that is actually wrong. Still, it's a bug affecting the regression tests, so patch all supported branches. In passing, remove dead variable "plstr", and demote "platt" to a local variable inside the PG_TRY block, since we don't need to clean it up in the PG_CATCH path.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions