Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g14Fl8l48730 for ; Mon, 4 Feb 2002 10:47:08 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g14Fl5f02304; Mon, 4 Feb 2002 10:47:05 -0500 (EST) To: Murray Prior Hobbs cc: pgsql-sql@postgresql.org Subject: Re: temporary tables, plpgsql and yes i bet this has been asked before In-reply-to: <3C5E6329.3000805@efone.com> References: <3C5E6329.3000805@efone.com> Comments: In-reply-to Murray Prior Hobbs message dated "Mon, 04 Feb 2002 21:32:09 +1100" Date: Mon, 04 Feb 2002 10:47:05 -0500 Message-ID: <2301.1012837625@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200202/40 X-Sequence-Number: 6472 Murray Prior Hobbs writes: > in a plpgsql function > create temporary table X > .... > drop table X You need to use EXECUTE for all accesses to the temp table, in order to defeat plpgsql's attempts to cache plans for those queries. regards, tom lane