rm_pg@xxxxxxxxxxxxxxxxxxxxxxx writes:
> I just wanted to make sure this change in behavior is
> a feature and not a bug.
Afraid so --- the plperl SRF support was rewritten in 8.1, and
it probably behaves just like plpgsql now, which has also got
this restriction.
> Is there an easy way of rewriting this construct where the results of
> a function can expand the result set that works nicely in 8.1?
A kluge some people have used with plpgsql is to put a SQL-language
wrapper function around the PL function, ie
create function foo(...) returns ... as
'select * from pl_foo(...)'
language sql;
Should work for plperl too.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
