]> granicus.if.org Git - postgresql/commit
Quick-and-dirty fix for recursive plpgsql functions, per bug report from
authorTom Lane <tgl@sss.pgh.pa.us>
Fri, 21 Sep 2001 00:11:31 +0000 (00:11 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Fri, 21 Sep 2001 00:11:31 +0000 (00:11 +0000)
commitae3129fd03928c1f5614370c79f1d69bd613f54b
treea470d068a4a70ac5920d82e5fbdb9455266bf6a5
parentac0c234c16fc94989aa6d695624aca073f0a7ab7
Quick-and-dirty fix for recursive plpgsql functions, per bug report from
Frank Miles 7-Sep-01.  This is really just sticking a finger in the dike.
Frank's case works now, but we still couldn't support a recursive function
returning a set.  Really need to restructure querytrees and execution
state so that the querytree is *read only*.  We've run into this over and
over and over again ... it has to happen sometime soon.
src/backend/executor/execQual.c
src/backend/utils/cache/fcache.c
src/include/utils/fcache.h
src/test/regress/expected/plpgsql.out
src/test/regress/sql/plpgsql.sql