Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id DEF1B47517F for ; Mon, 25 Mar 2002 19:35:24 -0500 (EST) 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 g2Q0Z8S05161; Mon, 25 Mar 2002 19:35:08 -0500 (EST) To: Jan Wieck Cc: Bruce Momjian , jack , pgsql-sql@postgresql.org Subject: Re: call the same pl/pgsql procedure twice in the same connection In-reply-to: <200203252136.g2PLaEg25650@saturn.janwieck.net> References: <200203252136.g2PLaEg25650@saturn.janwieck.net> Comments: In-reply-to Jan Wieck message dated "Mon, 25 Mar 2002 16:36:14 -0500" Date: Mon, 25 Mar 2002 19:35:07 -0500 Message-ID: <5158.1017102907@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200203/337 X-Sequence-Number: 7212 Jan Wieck writes: > This is somehow connected to the temporary view discussion, > as it needs the same detection if a query depends on > temporary objects. As soon as we have a detection mechanism > for it, I can modify PL/pgSQL not to save prepared plans for > these statements. Actually, I don't think plpgsql should make any special discrimination against temp tables; it should be able to re-use a query plan for exactly as long as the temp table exists. But I agree that we need a mechanism for tracking query-plan dependencies for this to happen. regards, tom lane