Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.2/8.9.1) with ESMTP id OAA42565; Mon, 1 Feb 1999 14:20:22 -0500 (EST) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id OAA23705; Mon, 1 Feb 1999 14:19:31 -0500 (EST) From: Bruce Momjian Message-Id: <199902011919.OAA23705@candle.pha.pa.us> Subject: Re: [HACKERS] Re: [COMMITTERS] [WEBMASTER] 'www/html main.html' In-Reply-To: from Jan Wieck at "Feb 1, 1999 8:12:16 pm" To: jwieck@debis.com Date: Mon, 1 Feb 1999 14:19:31 -0500 (EST) Cc: lockhart@alumni.caltech.edu, momjian@hub.org, hackers@postgreSQL.org, docs@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL47 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > OK, got to finish temp table and commit them first. > > Don't know if you noticed my statement in another thread. > > I think temp tables could confuse any function that uses the > prepared/saved plan feature of SPI manager. If such a > function called once saved a plan for a temp table named > 'test', and later called again but 'test' is now another > table, probably the parsetree and plan might point to the old > (wrong, not anymore existent) table. Yes. There are going to be limitations to the temp tables. Not sure how what the limitations are going to be.. -- Bruce Momjian | http://www.op.net/~candle maillist@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