Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 55C4063315D for ; Tue, 13 Apr 2010 13:43:01 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 78544-01-3 for ; Tue, 13 Apr 2010 16:42:50 +0000 (UTC) X-Greylist: delayed 00:07:35.976693 by SQLgrey-1.7.6 Received: from mail.deksai.com (mail.deksai.com [66.103.254.248]) by mail.postgresql.org (Postfix) with ESMTP id 1354F635A6F for ; Tue, 13 Apr 2010 13:02:56 -0300 (ADT) Received: from localhost (24-180-82-212.dhcp.bycy.mi.charter.com [24.180.82.212]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.deksai.com (Postfix) with ESMTPSA id E122F7441490 for ; Tue, 13 Apr 2010 11:55:18 -0400 (EDT) Date: Tue, 13 Apr 2010 11:55:18 -0400 From: Chris To: pgsql-performance@postgresql.org Subject: stats collector suddenly causing lots of IO Message-ID: <20100413155512.GA26542@chris-laptop.a2hosting.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.011 tagged_above=-10 required=5 tests=BAYES_20=-0.001, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201004/234 X-Sequence-Number: 38484 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. The versions of postgres that are running are: 8.1.18 8.2.6 8.3.1 8.3.5 8.3.6 8.3.7 8.3.8 8.3.9 8.4.2 8.4.3 I've tried turning off everything under RUNTIME STATISTICS in postgresql.conf except track_counts (since auto vacuum says it needs it), but it seems to have little affect on the IO caused by the stats collector. Has anyone else noticed this? Have there been recent kernel changes that could cause this that anyone knows about? Since we haven't touched postgres on these boxes since they were setup initially, I'm a bit baffled as to what might be causing the problem, and why I can't make it go away short of kill -STOP. Any suggestions would be much appreciated!