Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 6288C9FB2DD for ; Mon, 5 Mar 2007 15:30:31 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 79689-04 for ; Mon, 5 Mar 2007 15:30:11 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.190]) by postgresql.org (Postfix) with ESMTP id 82E959FB513 for ; Mon, 5 Mar 2007 15:30:11 -0400 (AST) Received: by mu-out-0910.google.com with SMTP id g7so1715447muf for ; Mon, 05 Mar 2007 11:30:10 -0800 (PST) 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=heCouEoLs4MgV647oj+5241jSpokARHh3dX5LUKeFqqUx5q4/US+iKEQtqfdGre9AcGo2XnfCQmkuur6l0r2oyERwhVOoREnmEHIPSO91P/Vmx4EFHDqvzLkIZh2wv/tWZ1bV377oZ35bzaCX4QozWnbEWVGJVN7Eq3MrE1YFU8= 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=sUwS8zzust8i9z0pdO7Ql0/KdZzGdElh04aqf9/0+YQqaGRuvS578CUzfBu9JYSZa6JtVvzWxNdYnu0GNaOlCK/lUjku0/jz+hh+UC8u4smdWhWRjTfkWAzJxCBbkNjwDHmh5VREkK9OrGrCH7aQ4Ct25CZlq26jHf8Fh0xqpgE= Received: by 10.82.111.8 with SMTP id j8mr5672205buc.1173123009928; Mon, 05 Mar 2007 11:30:09 -0800 (PST) Received: from ?192.168.1.34? ( [81.107.202.67]) by mx.google.com with ESMTP id y37sm15292434iky.2007.03.05.11.30.03; Mon, 05 Mar 2007 11:30:06 -0800 (PST) Message-ID: <45EC6FB8.8090603@enterprisedb.com> Date: Mon, 05 Mar 2007 19:30:00 +0000 From: Heikki Linnakangas User-Agent: Icedove 1.5.0.8 (X11/20061116) MIME-Version: 1.0 To: "Florian G. Pflug" CC: Tom Lane , ITAGAKI Takahiro , pgsql-hackers@postgresql.org, pgsql-patches@postgresql.org Subject: Re: [PATCHES] Aggressive freezing in lazy-vacuum References: <20070227141958.638D.ITAGAKI.TAKAHIRO@oss.ntt.co.jp> <20070227170613.GK29041@nasby.net> <20070305182401.C4BC.ITAGAKI.TAKAHIRO@oss.ntt.co.jp> <18982.1173110551@sss.pgh.pa.us> <45EC6F02.1050306@phlo.org> In-Reply-To: <45EC6F02.1050306@phlo.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: 200703/304 X-Sequence-Number: 99788 Florian G. Pflug wrote: > There could be a GUC vacuum_freeze_limit, and the actual FreezeLimit > would be calculated as > GetOldestXmin() - vacuum_freeze_limit We already have that. It's called vacuum_freeze_min_age, and the default is 100 million transactions. IIRC we added it late in the 8.2 release cycle when we changed the clog truncation point to depend on freeze limit. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com