X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5908AD85FC for ; Wed, 31 Aug 2005 11:39:51 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 60142-04 for ; Wed, 31 Aug 2005 14:39:49 +0000 (GMT) Received: from mx2.surnet.cl (mx2.surnet.cl [216.155.73.181]) by svr1.postgresql.org (Postfix) with ESMTP id C6833D85CE for ; Wed, 31 Aug 2005 11:39:47 -0300 (ADT) Received: from unknown (HELO cluster.surnet.cl) (216.155.73.164) by mx2.surnet.cl with ESMTP; 31 Aug 2005 10:39:06 -0400 X-IronPort-AV: i="3.96,158,1122868800"; d="scan'208"; a="4210992:sNHT3758395266" Received: from alvh.no-ip.org (216.155.78.140) by cluster.surnet.cl (7.0.043) (authenticated as alvherre@surnet.cl) id 42B3EF6000A9C80F; Wed, 31 Aug 2005 10:39:40 -0400 Received: by alvh.no-ip.org (Postfix, from userid 1000) id AC57AC2DC2A; Wed, 31 Aug 2005 10:40:09 -0400 (CLT) Date: Wed, 31 Aug 2005 10:40:09 -0400 From: Alvaro Herrera To: Tom Lane Cc: Jeff Frost , pgsql-admin@postgresql.org Subject: Re: auto vacuum settings Message-ID: <20050831144009.GB4864@surnet.cl> Mail-Followup-To: Tom Lane , Jeff Frost , pgsql-admin@postgresql.org References: <43152971.1030508@winklerpartners.com> <27988.1125463452@sss.pgh.pa.us> <1400.1125496055@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1400.1125496055@sss.pgh.pa.us> User-Agent: Mutt/1.5.10i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=2.254 required=5 tests=[AWL=-0.522, DNS_FROM_RFC_ABUSE=0.374, DNS_FROM_RFC_POST=1.376, RCVD_IN_NJABL_PROXY=1.026] X-Spam-Level: ** X-Archive-Number: 200508/414 X-Sequence-Number: 18733 On Wed, Aug 31, 2005 at 09:47:35AM -0400, Tom Lane wrote: > Jeff Frost writes: > > Since we're on the vacuum kick these days, what's the best way to tell if my > > autovacuum settings are working well? I'm sure I can query some info out of > > the pg_stats tables, no? > > If the database isn't bloating (ie, physical storage growing faster than > valid data volume) then it's getting the job done. Keep an eye on > "du $PGDATA" or pg_class.relpages entries. Another test may be checking table stats with pgstattuple. If the percentage of dead rows grows as time passes, you have a problem. -- Alvaro Herrera Architect, www.EnterpriseDB.com "Puedes vivir solo una vez, pero si lo haces bien, una vez es suficiente"