Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 51C0B9FBBDB for ; Wed, 16 May 2007 13:38:14 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 37222-02 for ; Wed, 16 May 2007 13:38:09 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id BA1BB9FBC7D for ; Wed, 16 May 2007 13:38:09 -0300 (ADT) Received: from perhan.alvh.no-ip.org (201-221-217-243.bk12-dsl.surnet.cl [201.221.217.243]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l4GGc7UL020499; Wed, 16 May 2007 09:38:08 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id B403832A13; Wed, 16 May 2007 12:38:04 -0400 (CLT) Date: Wed, 16 May 2007 12:38:04 -0400 From: Alvaro Herrera To: Heikki Linnakangas Cc: Tom Lane , Chris Browne , pgsql-patches@postgresql.org Subject: Re: [DOCS] Autovacuum and XID wraparound Message-ID: <20070516163804.GB4582@alvh.no-ip.org> References: <20070514011740.GH14860@fetter.org> <23394.1179108400@sss.pgh.pa.us> <1179117269.6047.3.camel@goldbach> <60sl9z6tln.fsf@dba2.int.libertyrms.com> <20070514221619.GC8916@alvh.no-ip.org> <857.1179184222@sss.pgh.pa.us> <20070515221347.GT12731@alvh.no-ip.org> <23362.1179292856@sss.pgh.pa.us> <20070516124420.GA4582@alvh.no-ip.org> <464B0E5A.1070807@enterprisedb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <464B0E5A.1070807@enterprisedb.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Wed, 16 May 2007 09:38:08 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/245 X-Sequence-Number: 2345 Heikki Linnakangas wrote: > Alvaro Herrera wrote: > >However, given that Heikki just confirmed that CLUSTER does not freeze > >tuples, it's not really possible to do this, so I'll drop the CLUSTER > >patch for now. > > > >This means that people using CLUSTER to compact tables won't have the > >benefit of advancing relfrozenxid, so they will have to run VACUUM on > >those tables at some point anyway, even though there will be no dead > >tuples :-( > > Now that I think this a bit more, I think CLUSTER should freeze the > tuples. I was worried about losing valuable debug information by doing > that, but thinking a bit more that's not a big concern: we wouldn't > freeze tuples newer than recent xmin. The update chain logic is the most > risky part of the code, and we wouldn't lose the xmin and xmax of tuples > that are part of update chains. > > Patch attached. You'll need the changes to cluster.c to set the > relfrozenid as well. Thanks, committed. (I changed NULL for InvalidBuffer). -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support