Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g14Klql14584 for ; Mon, 4 Feb 2002 15:47:52 -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 g14KlNf12148; Mon, 4 Feb 2002 15:47:24 -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: <200202042043.g14KhFl10735@candle.pha.pa.us> References: <200202042043.g14KhFl10735@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Mon, 04 Feb 2002 15:43:15 -0500" Date: Mon, 04 Feb 2002 15:47:23 -0500 Message-ID: <12145.1012855643@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200202/48 X-Sequence-Number: 6479 Bruce Momjian writes: >> * Allow row re-use without vacuum (Tom) > Well, a name doesn't mean someone claimed it but rather the _expert_ on > the item. I added this item assuming it was going to be accomplished > with some type of auto-vacuum. I will clearify it to mention > auto-vacuum, if that is OK. "Clarify"? How about "replace completely"? * Provide automatic scheduling of background vacuum Still not sure that I'd classify it as URGENT. regards, tom lane