X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id EB1669FA9BD for ; Tue, 2 May 2006 19:54:46 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 82077-09 for ; Tue, 2 May 2006 19:54:41 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 2F1C79FA2C7 for ; Tue, 2 May 2006 19:54:40 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 4AED956437; Tue, 2 May 2006 17:54:39 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Tue, 2 May 2006 17:54:38 -0500 Date: Tue, 2 May 2006 17:54:38 -0500 From: "Jim C. Nasby" To: Chris Mckenzie Cc: "'pgsql-performance@postgresql.org'" Subject: Re: Postgres 7.4 and vacuum_cost_delay. Message-ID: <20060502225438.GL97354@pervasive.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060502:chris.mckenzie@entrust.com::rkv1Ub+8bPclSRlh:00000000000 0000000000000000000000000qhz X-Hashcash: 1:20:060502:pgsql-performance@postgresql.org::Kp0oB5q2HiOaCSsw:00000 0000000000000000000000000L0S X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/55 X-Sequence-Number: 18842 On Tue, May 02, 2006 at 05:47:15PM -0400, Chris Mckenzie wrote: > Thanks. > > My first check was of course a grep/search of the postgres.conf, next it was > a complete source grep for vacuum_cost_delay. It's there in head... decibel@phonebook.1[17:52]~/pgsql/HEAD/src:4%grep -ri vacuum_cost_delay *|wc -l 8 > I've come to the conclusion I need to simply start tracking all transactions > and determining a cost/performance for the larger and frequently updated > tables without the benefit and penalty of pg_statio. Huh? pg_statio shouldn't present a large penalty AFAIK... -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461