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 g14EE3l29986 for ; Mon, 4 Feb 2002 09:14:04 -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 g14EDtM22394; Mon, 4 Feb 2002 09:13:55 -0500 (EST) From: Bruce Momjian Message-Id: <200202041413.g14EDtM22394@candle.pha.pa.us> Subject: Re: temporary tables, plpgsql and yes i bet this has been asked In-Reply-To: <3C5E6329.3000805@efone.com> To: Murray Prior Hobbs Date: Mon, 4 Feb 2002 09:13:54 -0500 (EST) CC: 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/38 X-Sequence-Number: 6470 Murray Prior Hobbs wrote: > > in a plpgsql function > > create temporary table X > > .... > > > drop table X > > > then in another function > > loop > > call the other function > > end loop > > > i get the problem that the second time the table is created (ie in the > second call) it is not visible > > now yes i could declare the table in the calling funtion but then the > original function is less useful to me Interesting. Can you recreate the problem in psql without the functions and show an example? I am confused how this could be failing. -- 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