aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistxlog.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2010-07-05 09:27:36 +0000
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2010-07-05 09:27:36 +0000
commit9e3a7f50e45315355a2a04fcf4cd7dc01f0a6840 (patch)
tree2d80c0600fbdd14c2e56e5cf7497157105c6074f /src/backend/access/gist/gistxlog.c
parent03795ffbc8e2f0c62422b6b9dc7b0fe1e6cdc0d9 (diff)
downloadpostgresql-9e3a7f50e45315355a2a04fcf4cd7dc01f0a6840.tar.gz
postgresql-9e3a7f50e45315355a2a04fcf4cd7dc01f0a6840.zip
The previous fix in CVS HEAD and 8.4 for handling the case where a cursor
being used in a PL/pgSQL FOR loop is closed was inadequate, as Tom Lane pointed out. The bug affects FOR statement variants too, because you can close an implicitly created cursor too by guessing the "<unnamed portal X>" name created for it. To fix that, "pin" the portal to prevent it from being dropped while it's being used in a PL/pgSQL FOR loop. Backpatch all the way to 7.4 which is the oldest supported version.
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions