Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id E5D526338A7 for ; Tue, 13 Apr 2010 18:55:38 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 79664-02 for ; Tue, 13 Apr 2010 21:55:21 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from spinlock.commandprompt.com (host-215.commandprompt.net [207.173.203.215]) by mail.postgresql.org (Postfix) with ESMTP id 528D1633881 for ; Tue, 13 Apr 2010 18:55:27 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by spinlock.commandprompt.com (Postfix) with ESMTP id D4258348036; Tue, 13 Apr 2010 14:55:25 -0700 (PDT) Received: from spinlock.commandprompt.com ([127.0.0.1]) by localhost (spinlock.commandprompt.com.commandprompt.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BxrCE1J9yvFx; Tue, 13 Apr 2010 14:55:25 -0700 (PDT) Received: from perhan.alvh.no-ip.org (unknown [190.95.6.149]) by spinlock.commandprompt.com (Postfix) with ESMTPSA id 6ABC1348035; Tue, 13 Apr 2010 14:55:25 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id ED9AD6E4A9; Tue, 13 Apr 2010 17:55:22 -0400 (CLT) Date: Tue, 13 Apr 2010 17:55:22 -0400 From: Alvaro Herrera To: Chris Cc: pgsql-performance@postgresql.org Subject: Re: stats collector suddenly causing lots of IO Message-ID: <20100413215522.GI2990@alvh.no-ip.org> References: <20100413170105.GA29571@chris-laptop.a2hosting.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100413170105.GA29571@chris-laptop.a2hosting.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.191 tagged_above=-10 required=5 tests=AWL=-0.291, BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201004/170 X-Sequence-Number: 38420 Chris wrote: > I have a lot of centos servers which are running postgres. Postgres isn't used > that heavily on any of them, but lately, the stats collector process keeps > causing tons of IO load. It seems to happen only on servers with centos 5. Does this correlate to an increase in size of the pgstat.stat file? Maybe you could try resetting stats, so that the file goes back to an initial size and is slowly repopulated. I'd suggest monitoring the size of the stats file, just in case there's something abnormal with it. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support