X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 195A8566D7 for ; Tue, 15 Mar 2005 23:51:36 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 69811-04 for ; Tue, 15 Mar 2005 23:51:27 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 4AA23566ED for ; Tue, 15 Mar 2005 23:51:26 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j2FNpJWf000819; Tue, 15 Mar 2005 18:51:19 -0500 (EST) To: Robert Treat Cc: Richard Huxton , Tambet Matiisen , pgsql-performance@postgresql.org Subject: Re: One tuple per transaction In-reply-to: <200503151652.30266.xzilla@users.sourceforge.net> References: <4236ACE5.1040004@archonet.com> <200503151652.30266.xzilla@users.sourceforge.net> Comments: In-reply-to Robert Treat message dated "Tue, 15 Mar 2005 16:52:30 -0500" Date: Tue, 15 Mar 2005 18:51:19 -0500 Message-ID: <818.1110930679@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/312 X-Sequence-Number: 11017 Robert Treat writes: > On a similar note I was just wondering if it would be possible to > mark any of these dead tuples as ready to be reused at transaction > commit time, since we know that they are dead to any and all other > transactions currently going on. I believe VACUUM already knows that xmin = xmax implies the tuple is dead to everyone. > This would save you from having to vacuum to get the tuples marked > ready for reuse. No; you forgot about reclaiming associated index entries. regards, tom lane