Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id A2FB3632831 for ; Tue, 25 May 2010 09:32:16 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 16668-08 for ; Tue, 25 May 2010 12:32:09 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mx3.wp.pl (mx3.wp.pl [212.77.101.7]) by mail.postgresql.org (Postfix) with ESMTP id F35066302EB for ; Tue, 25 May 2010 09:32:08 -0300 (ADT) Received: (wp-smtpd smtp.wp.pl 1586 invoked from network); 25 May 2010 14:31:51 +0200 Received: from 82-210-167-137.home.aster.pl (HELO [127.0.0.1]) (ipluta@[82.210.167.137]) (envelope-sender ) by smtp.wp.pl (WP-SMTPD) with AES256-SHA encrypted SMTP for ; 25 May 2010 14:31:51 +0200 Message-ID: <4BFBC336.1010709@wp.pl> Date: Tue, 25 May 2010 14:31:50 +0200 From: Ireneusz Pluta User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: jd@commandprompt.com CC: Doug Gorley , pgsql-admin@postgresql.org Subject: Re: How can I tell if I'm autovacuuming? References: <4BF7E14B.6030800@gorley.ca> <1274548283.8730.99.camel@jd-desktop.unknown.charter.com> In-Reply-To: <1274548283.8730.99.camel@jd-desktop.unknown.charter.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-WP-AV: skaner antywirusowy poczty Wirtualnej Polski S. A. X-WP-SPAM: NO 0000000 [MdOE] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.61 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201005/231 X-Sequence-Number: 34704 >> (b) How can I verify that my databases are being vacuumed by autovacuum? >> > > pg_stat_user_tables should have a last_autovac column. > Also, you can see autovacuum related messages like: DEBUG: autovacuum: processing database "postgres" DEBUG: autovacuum: processing database "template1" in your server log, by setting log_min_messages to 'debug1' in your postgresql.conf. As a side effect you may also see some other messages enabled with the same debug level,