Re: Plan invalidation design

From: "Merlin Moncure" <mmoncure(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Russell Smith" <mr-russ(at)pws(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Plan invalidation design
Date: 2007-02-18 22:41:23
Message-ID: b42b73150702181441i66beeb11k53bba136a985da56@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/19/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> > If you prepare "select *" and add a column, you're saying the query should
> > start failing?
>
> Either fail or change output; which you like better? The whole point of
> this exercise is to support plpgsql functions that do something like
>
> create temp table foo ...
> select * into rec from foo ...
> drop table foo ...

If that's the case, do you think there is a simpler way to handle this
problem than plan invalidation? Maybe I'm oversimplifying things a
bit here, but how about something like:

create local table foo ...
select * into rec from foo ...

this isn't completely unsurprising...we have 'SET LOCAL, etc.

merlin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Rief 2007-02-18 22:47:42 Re: Writing triggers in C++
Previous Message Guillaume Smet 2007-02-18 22:41:16 Re: n-gram search function