Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 8C0DE2FE69B for ; Mon, 30 Jul 2012 22:21:34 -0300 (ADT) Received: from [2404:130:0:10::40:2] (helo=mail.catalyst.net.nz) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Sw19P-0004EF-Ag for pgsql-performance@postgresql.org; Tue, 31 Jul 2012 01:21:33 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.catalyst.net.nz (Postfix) with ESMTP id 2D2C032D70; Tue, 31 Jul 2012 13:21:13 +1200 (NZST) X-Virus-Scanned: Debian amavisd-new at catalyst.net.nz Received: from mail.catalyst.net.nz ([127.0.0.1]) by localhost (bertrand.catalyst.net.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4YBgAvFmofte; Tue, 31 Jul 2012 13:21:12 +1200 (NZST) Received: from [IPv6:2404:130:0:1000:b419:dd7d:c30c:c6a3] (unknown [IPv6:2404:130:0:1000:b419:dd7d:c30c:c6a3]) (Authenticated sender: mark.kirkwood) by mail.catalyst.net.nz (Postfix) with ESMTPSA id 1848A32EF6; Tue, 31 Jul 2012 13:21:05 +1200 (NZST) Message-ID: <50173300.20800@catalyst.net.nz> Date: Tue, 31 Jul 2012 13:21:04 +1200 From: Mark Kirkwood User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0 MIME-Version: 1.0 To: David Barton CC: Tom Lane , pgsql-performance@postgresql.org Subject: Re: Postgres 9.1.4 - high stats collector IO usage References: <50136B8D.7070502@oneit.com.au> <29996.1343492034@sss.pgh.pa.us> <50141C7A.4050607@oneit.com.au> In-Reply-To: <50141C7A.4050607@oneit.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2404:130:0:10::40:2 (failed) X-Pg-Spam-Score: 0.3 (/) X-Archive-Number: 201207/355 X-Sequence-Number: 47536 On 29/07/12 05:08, David Barton wrote: > Thanks so much, Tom. > > That did the job. I increased it to every 15 minutes and it has > dropped substantially even though the pgstat.stat file is over 1 MB > again. > > I'd be a little concerned that having autovacuum tuned down to run so infrequently might result in massive table bloat - which could be even worse than than the original stats file problem. Keep an eye out for any table(s) that used to be small but become unexpectedly larger over the next few days, and if you see any then decrease the naptime again. Regards Mark