-
- Downloads
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.
Showing
- src/backend/executor/execQual.c 61 additions, 44 deletionssrc/backend/executor/execQual.c
- src/backend/utils/cache/fcache.c 8 additions, 24 deletionssrc/backend/utils/cache/fcache.c
- src/include/utils/fcache.h 20 additions, 24 deletionssrc/include/utils/fcache.h
- src/test/regress/expected/plpgsql.out 19 additions, 0 deletionssrc/test/regress/expected/plpgsql.out
- src/test/regress/sql/plpgsql.sql 15 additions, 0 deletionssrc/test/regress/sql/plpgsql.sql
Loading
Please register or sign in to comment