X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id CE4B2D1D5A4 for ; Wed, 19 Nov 2003 06:33:08 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 05764-06 for ; Wed, 19 Nov 2003 02:32:38 -0400 (AST) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by svr1.postgresql.org (Postfix) with ESMTP id 98256D1B53A for ; Wed, 19 Nov 2003 02:32:36 -0400 (AST) Received: from myrealbox.com shridhar_daithankar@smtp-send.myrealbox.com [202.54.11.72] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.44 $ on Novell NetWare via secured & encrypted transport (TLS); Tue, 18 Nov 2003 23:32:28 -0700 Message-ID: <3FBB0E77.4020105@myrealbox.com> Date: Wed, 19 Nov 2003 12:02:23 +0530 From: Shridhar Daithankar User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: josh@agliodbs.com Cc: pgsql-performance@postgresql.org Subject: Re: More detail on settings for pgavd? References: <200311181558.45847.josh@agliodbs.com> In-Reply-To: <200311181558.45847.josh@agliodbs.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/149 X-Sequence-Number: 4709 Josh Berkus wrote: > Shridhar, > > I was looking at the -V/-v and -A/-a settings in pgavd, and really don't > understand how the calculation works. According to the readme, if I set -v > to 1000 and -V to 2 (the defaults) for a table with 10,000 rows, pgavd would > only vacuum after 21,000 rows had been updated. This seems wrong. > > Can you clear this up a little? I'd like to tweak these settings but can't > without being better aquainted with the calculation. > > Also, you may want to reverse your default ratio for Vacuum/analyze frequency. > True, analyze is a less expensive operation than Vacuum, but it's also needed > less often -- only when the *distribution* of data changes. I've seen > databases where the optimal vacuum/analyze frequency was every 10 min/once > per day. Will look into it. Give me a day or so. I am planning couple of other patches as well. May be over week end. Is this urgent? Shridhar