Received: from smtp013.mail.yahoo.com (smtp013.mail.yahoo.com [216.136.173.57]) by postgresql.org (8.11.3/8.11.4) with SMTP id g14LJhl30218 for ; Mon, 4 Feb 2002 16:19:43 -0500 (EST) (envelope-from janwieck@yahoo.com) Received: from psc.progress.com (HELO saturn.janwieck.net) (192.233.92.200) by smtp.mail.vip.sc5.yahoo.com with SMTP; 4 Feb 2002 21:19:12 -0000 Received: (from wieck@localhost) by saturn.janwieck.net (8.11.2/8.11.2) id g14LDZF01956; Mon, 4 Feb 2002 16:13:35 -0500 From: Jan Wieck Message-Id: <200202042113.g14LDZF01956@saturn.janwieck.net> Subject: Re: temporary tables, plpgsql and yes i bet this has been asked In-Reply-To: <11996.1012854355@sss.pgh.pa.us> from Tom Lane at "Feb 4, 2002 03:25:55 pm" To: Tom Lane Date: Mon, 4 Feb 2002 16:13:34 -0500 (EST) CC: Jan Wieck , Bruce Momjian , Murray Prior Hobbs , pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200202/49 X-Sequence-Number: 6480 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? 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