Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 1C80D6326F5 for ; Fri, 16 Apr 2010 15:15:08 -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 41274-03 for ; Fri, 16 Apr 2010 18:14:54 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by mail.postgresql.org (Postfix) with ESMTP id 3167E632757 for ; Fri, 16 Apr 2010 15:14:57 -0300 (ADT) Received: from [192.168.0.105] (pool-96-244-14-10.bltmmd.fios.verizon.net [96.244.14.10]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0LuHL9-1NMfZx3MF5-011g7h; Fri, 16 Apr 2010 20:14:55 +0200 Message-ID: <4BC8A91D.9030709@2ndquadrant.com> Date: Fri, 16 Apr 2010 14:14:53 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Josh Kupershmidt CC: Tom Lane , Chris , pgsql-performance@postgresql.org Subject: Re: stats collector suddenly causing lots of IO References: <20100413170105.GA29571@chris-laptop.a2hosting.com> <25952.1271370711@sss.pgh.pa.us> <9738.1271431432@sss.pgh.pa.us> <10082.1271432484@sss.pgh.pa.us> <11152.1271436528@sss.pgh.pa.us> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX19iAWpclLFS+ekbfOrPtNPfih/+8D9R10c9Vdb ClnUrDAukfmFcjg3u8Y/fT/QdNuBwNKbVxOAxGOe4tCI8A56Iw R3ZMuywZad+20Ys0fsT0jW8mXUdNvUf X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.986 tagged_above=-10 required=5 tests=AWL=-0.086, BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201004/222 X-Sequence-Number: 38472 Josh Kupershmidt wrote: > SELECT name, current_setting(name), source FROM pg_settings WHERE > source != 'default' AND name ILIKE '%vacuum%'; > name | current_setting | source > ----------------------+-----------------+-------------------- > vacuum_cost_delay | 200ms | configuration file > vacuum_cost_limit | 100 | configuration file > vacuum_cost_page_hit | 6 | configuration file > > > Hopefully changing those three vacuum_cost_* params will speed up the > manual- and auto-vacuums.. Those only impact manual VACUUM statements. There's a different set with names like autovacuum_vacuum_cost_delay that control the daemon. You can set those to "-1" in order to match the regular VACUUM, but that's not the default. You really need to sort out the max_fsm_pages setting too, because until that issue goes away these tables are unlikely to ever stop growing. And, no, you can't use CLUSTER on the system tables to clean those up. -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us