From: Kevin Kempter <kevink@consistentstate.com>
To: pgsql-admin@postgresql.org
Subject: Re: vacuum monitoring question
Date: Wed, 24 Dec 2008 12:09:40 -0700
Message-ID: <200812241209.40471.kevink@consistentstate.com> (raw)
In-Reply-To: <dcc563d10812240856n2bd22623jae27129914db27bc@mail.gmail.com>
References: <200812240931.53278.kevink@consistentstate.com>
<dcc563d10812240856n2bd22623jae27129914db27bc@mail.gmail.com>
On Wednesday 24 December 2008 09:56:29 Scott Marlowe wrote:
> On Wed, Dec 24, 2008 at 9:31 AM, Kevin Kempter
>
> <kevink@consistentstate.com> wrote:
> > Hi All;
> >
> > I'm working on a vacuum monitor script to alert us when tables start to
> > grow out of control per dead space. Initially I excluded the system
> > catalog schemas (pg_catalog, pg_toast, etc) however I wonder if maybe I
> > should monitor these as well. PLus I'm looking for any input as to
> > specifically what to look for - I've calculated a 'fill factor' which
> > shows the average page fill as a percentage but I wonder what other
> > metrics may help monitor possible problem tables effeciently..
>
> It's a good idea to keep an eye on system catalogs, especially if you
> have a fair bit of DDL going on in your usage. I'd take a look at
> what the check_postgresql.pl script does. No need to reproduce all
> that work on your own.
Thanks for the feedback - where can I find the check_postgresql.pl script ?
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: kevink@consistentstate.com
Subject: Re: vacuum monitoring question
In-Reply-To: <200812241209.40471.kevink@consistentstate.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