summaryrefslogtreecommitdiff
path: root/src/test/thread
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2010-07-05 09:27:18 +0000
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2010-07-05 09:27:18 +0000
commiteb81b6509f4c9109ecf8839d8c482cc597270687 (patch)
treebdf77cd59647f8e932ddaf8774f90cc2ab901b4d /src/test/thread
parent2330d9c1475a70385b116fda6cc54ac2cc2939c4 (diff)
downloadpostgresql-eb81b6509f4c9109ecf8839d8c482cc597270687.tar.gz
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/test/thread')
0 files changed, 0 insertions, 0 deletions