Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 65AB364FDA2 for ; Wed, 24 Dec 2008 15:09:55 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 65634-03 for ; Wed, 24 Dec 2008 15:09:50 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180]) by mail.postgresql.org (Postfix) with ESMTP id A011F64FD3D for ; Wed, 24 Dec 2008 15:09:49 -0400 (AST) Received: by wa-out-1112.google.com with SMTP id j4so1867048wah.19 for ; Wed, 24 Dec 2008 11:09:48 -0800 (PST) Received: by 10.114.124.1 with SMTP id w1mr5702154wac.132.1230145788190; Wed, 24 Dec 2008 11:09:48 -0800 (PST) Received: from issac.consistentstate.com (c-75-71-181-91.hsd1.co.comcast.net [75.71.181.91]) by mx.google.com with ESMTPS id n22sm11757803pof.2.2008.12.24.11.09.45 (version=SSLv3 cipher=RC4-MD5); Wed, 24 Dec 2008 11:09:46 -0800 (PST) From: Kevin Kempter Organization: Consistent State To: pgsql-admin@postgresql.org Subject: Re: vacuum monitoring question Date: Wed, 24 Dec 2008 12:09:40 -0700 User-Agent: KMail/1.10.3 (Linux/2.6.27.7-134.fc10.x86_64; KDE/4.1.3; x86_64; ; ) References: <200812240931.53278.kevink@consistentstate.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="Boundary-00=_0joUJVqzgSDa+ax" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200812241209.40471.kevink@consistentstate.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200812/187 X-Sequence-Number: 31020 --Boundary-00=_0joUJVqzgSDa+ax Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit On Wednesday 24 December 2008 09:56:29 Scott Marlowe wrote: > On Wed, Dec 24, 2008 at 9:31 AM, Kevin Kempter > > 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 ? --Boundary-00=_0joUJVqzgSDa+ax Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: 7bit

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 ?

--Boundary-00=_0joUJVqzgSDa+ax--