Received: from candle.pha.pa.us (216-55-132-35.dsl.san-diego.abac.net [216.55.132.35]) by postgresql.org (Postfix) with ESMTP id 27CB3475452 for ; Thu, 18 Apr 2002 13:22:23 -0400 (EDT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id g3IHMEc21830; Thu, 18 Apr 2002 13:22:14 -0400 (EDT) From: Bruce Momjian Message-Id: <200204181722.g3IHMEc21830@candle.pha.pa.us> Subject: Re: call the same pl/pgsql procedure twice in the same connection In-Reply-To: <200204181643.g3IGhUw14564@saturn.janwieck.net> To: Jan Wieck Date: Thu, 18 Apr 2002 13:22:14 -0400 (EDT) Cc: jack , pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL97 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200204/233 X-Sequence-Number: 7497 Jan Wieck wrote: > Bruce Momjian wrote: > > > > Jan, instead of doing cache invalidation to fix temporary tables, can we > > disable cached plans for functions that use temporary tables? > > I was thinking of a different approach. Enhancing the SPI > manager to detect if a plan uses temporary objects and to > remember the original querystring in the SPI_plan. Having > callbacks when temp object beeing destroyed into the SPI > manager, causing it to reparse and plan on the next call to > SPI_execp() would do it for everything that uses SPI. I was merely proposing that preventing caching of functions ueing temp tables may be easier than trying to invalidation them on temp table destruction. -- 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