Обсуждение: Re: temporary tables, plpgsql and yes i bet this has been asked

Tom Lane wrote:
> Jan Wieck <janwieck@yahoo.com> writes:
> >     SPI still needs to learn how to determine  if  a  query  uses
> >     temp tables somewhere in order to silently re-prepare queries
> >     when required.  And I am absolutely sure this is not an issue
> >     we should address in PL/pgSQL. It has to be solved on the SPI
> >     level.
> 
> Temp tables are the wrong way to think about it.  *Any* invalidation
> of schema data referred to in a query plan should cause replanning.
> We have a TODO item covering this already, don't we?

If we do, I don't see it.  Care to give me one?  I am not sure how to
word it.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 

Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Tom Lane wrote:
>> Temp tables are the wrong way to think about it.  *Any* invalidation
>> of schema data referred to in a query plan should cause replanning.
>> We have a TODO item covering this already, don't we?

> If we do, I don't see it.  Care to give me one?

Hmm, I don't see one either.  Odd, we've sure discussed it often enough.
How about

* Flush cached query plans when their underlying catalog data changes

Probably belongs under "DEPENDENCY CHECKING".


BTW, I was slightly startled to read this under URGENT:

* Allow row re-use without vacuum (Tom)

I don't consider this urgent or even likely ever to happen, and
I certainly have not taken responsibility to do it.
        regards, tom lane