On Fri, 5 Oct 2001, Bruce Momjian wrote:
>
> What actually should happen is that the view should go away at the end
> of the session. However, unlike indexes, we can have several tables
> involved in a view so it is hard to know exactly how to handle this.
>
> Seems like a TODO item, at least. What we could do is to create views
> as TEMP if they use temp tables and drop the view as soon as the session
> ends . You of course would have to recreate the view each time but
> because it is a _temp_ view, it could be done reliably by multiple
> backends at the same time.
Didn't someone suggest dropping saving of parsed plans with OIDs
altogether, and saving the underlying query instead? The point was that
parser and planner are fast enough to make it unnecessary to save plans.
I don't remember what was disposition of that idea....
-alex
