> CREATE OR REPLACE FUNCTION test() RETURNS integer AS
> _r RECORD;
> CREATE TEMP TABLE test(id int);
> _r := ROW(NULL)::test;
> DROP TABLE test CASCADE;
> RETURN 1;
> LANGUAGE plpgsql VOLATILE
> COST 100;
Hmm. The problem with this is that the DROP TABLE invalidates test's
rowtype, so on a second call the already-compiled "ROW(NULL)::test"
expression refers to a type that no longer exists.
We could fix that by adding datatypes to the set of objects that are
tracked to determine when a cached plan must be invalidated, but I'm
more than a bit hesitant to expend the extra cycles for this, given
the lack of previous complaints and the large number of datatypes
that are mentioned in most plans.
Perhaps it would be good enough to only track types that must be
rowtypes (ie, are mentioned in RowExpr or ConvertRowtypeExpr)?
regards, tom lane
In response to
pgsql-bugs by date
|Next:||From: Sachin Srivastava||Date: 2012-06-27 05:40:15|
|Subject: Re: BUG #6705: 32 bit|
|Previous:||From: digoal||Date: 2012-06-27 00:02:53|
|Subject: BUG #6708: pgsql_fdw's foreign table cann't used in plpgsql function|