Re: RangeTblEntry modifications - Mailing list pgsql-hackers

From Alex Pilosov
Subject Re: RangeTblEntry modifications
Date
Msg-id Pine.BSO.4.10.10107010857360.7004-100000@spider.pilosoft.com
Whole thread Raw
In response to Re: RangeTblEntry modifications  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, 1 Jul 2001, Tom Lane wrote:

> Alex Pilosov <alex@pilosoft.com> writes:
> > I think I just understood what you were saying: having tupleDesc in RTE is
> > not kosher, because RTE can last longer than a given tupleDesc?
> 
> Depends where you got the tupleDesc from --- if you copy it into the
> parse context then it's OK in terms of not disappearing.  However,
> that doesn't mean it's still *valid*.  Consider
> 
>     begin;
>     declare foo cursor for select * from bar;
>     create view v1 as select * from cursor foo;
>     end;
> 
> Now the cursor foo is no more, but v1 still exists ... what happens
> when we try to select from v1?
I believe it will fail in the executor trying to open the portal...That's
the expected behaviour, right?

-alex 



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: RangeTblEntry modifications
Next
From: Tom Lane
Date:
Subject: Re: functions returning sets