Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g14Kdrl12413 for ; Mon, 4 Feb 2002 15:39:53 -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 g14KdLf12071; Mon, 4 Feb 2002 15:39:21 -0500 (EST) To: Bruce Momjian cc: Jan Wieck , Murray Prior Hobbs , pgsql-sql@postgresql.org Subject: Re: temporary tables, plpgsql and yes i bet this has been asked In-reply-to: <200202042027.g14KR6n07132@candle.pha.pa.us> References: <200202042027.g14KR6n07132@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Mon, 04 Feb 2002 15:27:06 -0500" Date: Mon, 04 Feb 2002 15:39:20 -0500 Message-ID: <12068.1012855160@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200202/46 X-Sequence-Number: 6477 Bruce Momjian writes: > Tom Lane wrote: >> Temp tables are the wrong way to think about it. *Any* invalidation >> of schema data referred to in a query plan should cause replanning. >> We have a TODO item covering this already, don't we? > If we do, I don't see it. Care to give me one? Hmm, I don't see one either. Odd, we've sure discussed it often enough. How about * Flush cached query plans when their underlying catalog data changes Probably belongs under "DEPENDENCY CHECKING". BTW, I was slightly startled to read this under URGENT: * Allow row re-use without vacuum (Tom) I don't consider this urgent or even likely ever to happen, and I certainly have not taken responsibility to do it. regards, tom lane