Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g14KQOl08104 for ; Mon, 4 Feb 2002 15:26:24 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g14KPuf11999; Mon, 4 Feb 2002 15:25:56 -0500 (EST) To: Jan Wieck cc: Bruce Momjian , Murray Prior Hobbs , pgsql-sql@postgresql.org Subject: Re: temporary tables, plpgsql and yes i bet this has been asked In-reply-to: <200202042006.g14K6QR01773@saturn.janwieck.net> References: <200202042006.g14K6QR01773@saturn.janwieck.net> Comments: In-reply-to Jan Wieck message dated "Mon, 04 Feb 2002 15:06:26 -0500" Date: Mon, 04 Feb 2002 15:25:55 -0500 Message-ID: <11996.1012854355@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200202/44 X-Sequence-Number: 6476 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? regards, tom lane