DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=qXGnNToNKOXzLucYZOOrHGmVdgziSuFAmuNRvCxv/3eeBHEDNifYXv5rSqZL0enLE0bfsSrIgtmLJWaoQoYtai7oD7QR0bQ1W75+AMSk8QaiIaKSgmwrfL/LgEaQVyO7gRK9rhIYwl6aMTt6VT9bd+xCCE/0TQx6W6agrQFTwYk=
Message-ID: <47FB20D4.3050504@gmail.com>
Date: Tue, 08 Apr 2008 00:37:56 -0700
From: paul rivers <rivers.paul@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080227)
MIME-Version: 1.0
To: Michael Monnerie <michael.monnerie@it-management.at>
CC: pgsql-admin@postgresql.org
Subject: Re: Tuning
References: <6F737A76-FC25-4876-A6E0-163B87ECFAB0@indiana.edu>
	<dcc563d10804070927t29a3fe36qed0c03198a67e7c1@mail.gmail.com>
	<200804080917.27689@zmi.at>
In-Reply-To: <200804080917.27689@zmi.at>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Michael Monnerie wrote:
> On Montag, 7. April 2008 Scott Marlowe wrote:
>   
>> You can monitor things like index and table bloat with the pg_stat_*
>> series of views.
>>     
>
> Are there scripts to automate this look at stats?
> Or could one draw graphs from that values, to visualize how well the db 
> is? E.g., if you could calculate a % value, you could make RRD stats to 
> see it's change over time. Is there any project on this?
>
> mfg zmi
>   


I don't see a direct way to monitor bloat from pg_stat*.   If I'm wrong, 
please set me straight.

For example, monitoring index bloat would involve deciding how many 
pages an index would ideally consume, based on either sampling the table 
yourself or raiding stats, and making assumptions.  Then you'd compare 
to actual (or approximated actual) and decide if you were within 
whatever threshold you think is OK.

Paul