From: paul rivers <rivers.paul@gmail.com>
To: Michael Monnerie <michael.monnerie@it-management.at>
Cc: pgsql-admin@postgresql.org
Subject: Re: Tuning
Date: Tue, 08 Apr 2008 00:37:56 -0700
Message-ID: <47FB20D4.3050504@gmail.com> (raw)
In-Reply-To: <200804080917.27689@zmi.at>
References: <6F737A76-FC25-4876-A6E0-163B87ECFAB0@indiana.edu>
<dcc563d10804070927t29a3fe36qed0c03198a67e7c1@mail.gmail.com>
<200804080917.27689@zmi.at>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: rivers.paul@gmail.com, michael.monnerie@it-management.at
Subject: Re: Tuning
In-Reply-To: <47FB20D4.3050504@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox