Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id B14749FC32A for ; Fri, 22 Jun 2007 10:55:26 -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 18637-06 for ; Fri, 22 Jun 2007 10:55:17 -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 39EF39FC0F5 for ; Fri, 22 Jun 2007 10:55:22 -0300 (ADT) Received: from perhan.alvh.no-ip.org (201-220-125-150.bk10-dsl.surnet.cl [201.220.125.150]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l5MDtHmA020236; Fri, 22 Jun 2007 06:55:18 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 87F0332A29; Fri, 22 Jun 2007 09:55:04 -0400 (CLT) Date: Fri, 22 Jun 2007 09:55:04 -0400 From: Alvaro Herrera To: Steven Flatt Cc: Bill Moran , Francisco Reyes , pgsql-performance@postgresql.org Subject: Re: Database-wide VACUUM ANALYZE Message-ID: <20070622135504.GA8949@alvh.no-ip.org> References: <357fa7590706211009w2ef6071fn83c5759db6be1e80@mail.gmail.com> <357fa7590706211236y2856ed96q5394b9302b9a528f@mail.gmail.com> <20070621160732.58497e2b.wmoran@collaborativefusion.com> <357fa7590706211337i55e9b20nea5a1bd4c5e41268@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <357fa7590706211337i55e9b20nea5a1bd4c5e41268@mail.gmail.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]); Fri, 22 Jun 2007 06:55:18 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/537 X-Sequence-Number: 25570 Steven Flatt escribió: > Thanks everyone. It appears that we had hacked the 502.pgsql script for our > 8.1 build to disable the daily vacuum. I was not aware of this when > building and upgrading to 8.2. > > So it looks like for the past two weeks, that 36 hour db-wide vacuum has > been running every 24 hours. Good for it for being reasonably non-intrusive > and going unnoticed until now. :) Looks like you have plenty of spare I/O ;-) > Although apparently not related anymore, I still think it was a good move to > change autovacuum_freeze_max_age from 200 million to 2 billion. Absolutely not related. Also note that 1. autovacuum is not able (in 8.2 or older) to have more than one task running 2. autovacuum in 8.2 doesn't ever launch database-wide vacuums. As of 8.2 it only vacuums tables that are in actual danger of Xid wraparound (according to pg_class.relfrozenxid); tables that had been vacuumed the day before would not need another vacuum for Xid purposes (though if you had modified the table to the point that it needed another vacuum, that would be another matter). Unless you consumed 200 million (or 2 billion) transactions during the day, that is. -- Alvaro Herrera http://www.amazon.com/gp/registry/5ZYLFMCVHXC "The only difference is that Saddam would kill you on private, where the Americans will kill you in public" (Mohammad Saleh, 39, a building contractor)