aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/functioncmds.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2010-07-05 09:27:49 +0000
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2010-07-05 09:27:49 +0000
commitc778f898188e931bfefda02c97c37864858f14de (patch)
treebeafca84c52487176bc0d3daecefe95bd7aafbbd /src/backend/commands/functioncmds.c
parent971e11028f67770e3d782cfeb1d4115477ace49a (diff)
downloadpostgresql-c778f898188e931bfefda02c97c37864858f14de.tar.gz
postgresql-c778f898188e931bfefda02c97c37864858f14de.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/commands/functioncmds.c')
0 files changed, 0 insertions, 0 deletions