Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 6ADF59FBB40 for ; Wed, 16 May 2007 05:22:17 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 18684-05 for ; Wed, 16 May 2007 05:22:10 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.227]) by postgresql.org (Postfix) with ESMTP id 1B4699FBA41 for ; Wed, 16 May 2007 05:22:13 -0300 (ADT) Received: by wx-out-0506.google.com with SMTP id i28so91853wxd for ; Wed, 16 May 2007 01:22:12 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=sgHS+fkjwG3Xoo91yogTpddzsjSNLqufdUAbNVGIgEthO9HE0LEbfC+X0tSmsTpgwLj7U6UFjVMJKagzPh0XdF9xuqhEJd0fUiLuX40N4xxnttpJ/T2Qzv4qGIZMwjOi/oNNm+rC7D/9zpd+ecWoYLpOtuSx7ROIMDC62mVPPZ8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=pmT1JS8IKNk8ItuxkExAKJk63XCMw3yop7t2p/igNTzAzlpMDY8dEa/Korllr4MZd1xkbRFrxPQkotRuws6iaCEuZNNgdF4gPgycZVPaSPqh/d2lFWmqofDRHMenIcO2cRGUfyx6kZP+bzxUjviwCNZKb8zDfYmXdSL56firXyE= Received: by 10.90.86.10 with SMTP id j10mr7505164agb.1179303732192; Wed, 16 May 2007 01:22:12 -0700 (PDT) Received: from ?192.168.1.33? ( [82.3.78.153]) by mx.google.com with ESMTP id l48sm2007675wrl.2007.05.16.01.22.09; Wed, 16 May 2007 01:22:10 -0700 (PDT) Message-ID: <464ABF2A.3000005@enterprisedb.com> Date: Wed, 16 May 2007 09:22:02 +0100 From: Heikki Linnakangas User-Agent: Icedove 1.5.0.10 (X11/20070329) MIME-Version: 1.0 To: Alvaro Herrera CC: "Jim C. Nasby" , Tom Lane , Chris Browne , pgsql-patches@postgresql.org, Heikki Linnakangas Subject: Re: [DOCS] Autovacuum and XID wraparound 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> <20070516002500.GG20707@nasby.net> <20070516020218.GX12731@alvh.no-ip.org> In-Reply-To: <20070516020218.GX12731@alvh.no-ip.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/230 X-Sequence-Number: 2330 Alvaro Herrera wrote: > In any case the change is a very small patch, which I attach but I > haven't tested. This only works if the new rewriteheap stuff actually > changes Xids to follow OldestXmin, i.e. all tuples that have older > Xmin/Xmax are frozen (or marked with the current Xid). Heikki, can you > confirm that this is the case? No, CLUSTER doesn't freeze tuples. It could do that easily, it didn't occur to me when I wrote it. It would make it harder to debug, though, should we have any problems with it in the future. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com