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 g14KFgl02176 for ; Mon, 4 Feb 2002 15:15:42 -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 g14KFUU04173; Mon, 4 Feb 2002 15:15:30 -0500 (EST) From: Bruce Momjian Message-Id: <200202042015.g14KFUU04173@candle.pha.pa.us> Subject: Re: temporary tables, plpgsql and yes i bet this has been asked In-Reply-To: <200202042006.g14K6QR01773@saturn.janwieck.net> To: Jan Wieck Date: Mon, 4 Feb 2002 15:15:30 -0500 (EST) CC: 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/42 X-Sequence-Number: 6474 > I bet he's using the temp table without EXECUTE. That > would've failed even without the other "calling" function > around it, as soon as he uses it more than once per session. > > 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. Will this still be an issue with schemas? I am thinking no. -- 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