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.
portalmem.c (r1.62 -> r184.108.40.206)
portal.h (r1.47 -> r220.127.116.11)
pl_exec.c (r18.104.22.168 -> r22.214.171.124)
pgsql-committers by date
|Next:||From: User Andrewd||Date: 2010-07-05 16:28:14|
|Subject: pgbuildfarm - client-code: Accomodate oddities in at least some versions |
|Previous:||From: Heikki Linnakangas||Date: 2010-07-05 09:27:49|
|Subject: pgsql: The previous fix in CVS HEAD and 8.4 for handling the case where |