From: Jan Wieck <janwieck@yahoo.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jan Wieck <janwieck@yahoo.com>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Murray Prior Hobbs <murray@efone.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: temporary tables, plpgsql and yes i bet this has been asked
Date: Mon, 4 Feb 2002 16:13:34 -0500 (EST)
Message-ID: <200202042113.g14LDZF01956@saturn.janwieck.net> (raw)
In-Reply-To: <11996.1012854355@sss.pgh.pa.us>
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?
Of course, still. Nothing changed on that since we discussed
it the last time ;-P
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: janwieck@yahoo.com, tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, murray@efone.com
Subject: Re: temporary tables, plpgsql and yes i bet this has been asked
In-Reply-To: <200202042113.g14LDZF01956@saturn.janwieck.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox