From: | tgl(at)postgresql(dot)org |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql/src backend/executor/execQual.c backend/ ... |
Date: | 2001-09-21 00:11:31 |
Message-ID: | 200109210011.f8L0BV884556@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
CVSROOT: /cvsroot
Module name: pgsql
Changes by: tgl(at)postgresql(dot)org 01/09/20 20:11:31
Modified files:
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
Log message:
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.
From | Date | Subject | |
---|---|---|---|
Next Message | tgl | 2001-09-21 03:32:36 | pgsql/ oc/src/sgml/runtime.sgml rc/backend/com ... |
Previous Message | tgl | 2001-09-20 23:31:08 | pgsql/src/backend/parser parse_expr.c |