Received: from candle.pha.pa.us (216-55-132-35.dsl.san-diego.abac.net [216.55.132.35]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g14KRMl08790 for ; Mon, 4 Feb 2002 15:27:22 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id g14KR6n07132; Mon, 4 Feb 2002 15:27:06 -0500 (EST) From: Bruce Momjian Message-Id: <200202042027.g14KR6n07132@candle.pha.pa.us> Subject: Re: temporary tables, plpgsql and yes i bet this has been asked In-Reply-To: <11996.1012854355@sss.pgh.pa.us> To: Tom Lane Date: Mon, 4 Feb 2002 15:27:06 -0500 (EST) CC: Jan Wieck , Murray Prior Hobbs , pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL96 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200202/43 X-Sequence-Number: 6475 Tom Lane wrote: > Jan Wieck 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, Pennsylvania 19026