Re: pgsql/ oc/src/sgml/func.sgml oc/src/sgml/relea ... - Mailing list pgsql-committers

From Peter Eisentraut
Subject Re: pgsql/ oc/src/sgml/func.sgml oc/src/sgml/relea ...
Date
Msg-id Pine.LNX.4.44.0205191426500.916-100000@localhost.localdomain
Whole thread Raw
In response to Re: pgsql/ oc/src/sgml/func.sgml oc/src/sgml/relea ...  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql/ oc/src/sgml/func.sgml oc/src/sgml/relea ...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
Tom Lane writes:

> Hmm.  Have you tried this with recursive plpgsql functions?  I have a
> feeling that that little hack of replacing the flinfo link isn't gonna
> work well in plpgsql, because of its caching of query plans.

I don't understand what specific problem you are referring to.  As long as
each function is only caching its own query plans in its own fn_extra area
then things shouldn't work differently from before.

--
Peter Eisentraut   peter_e@gmx.net


pgsql-committers by date:

Previous
From: petere@postgresql.org (Peter Eisentraut - PostgreSQL)
Date:
Subject: pgsql/src/test/regress expected/privileges.out ...
Next
From: petere@postgresql.org (Peter Eisentraut - PostgreSQL)
Date:
Subject: pgsql/src/backend/parser gram.y