Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 5F6EF6501F2 for ; Wed, 24 Dec 2008 12:37:31 -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 40595-01-7 for ; Wed, 24 Dec 2008 12:37:28 -0400 (AST) X-Greylist: delayed 00:05:30.664717 by SQLgrey-1.7.6 Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168]) by mail.postgresql.org (Postfix) with ESMTP id A2C03650142 for ; Wed, 24 Dec 2008 12:37:28 -0400 (AST) Received: by wf-out-1314.google.com with SMTP id 25so3134457wfc.28 for ; Wed, 24 Dec 2008 08:37:27 -0800 (PST) Received: by 10.143.28.8 with SMTP id f8mr3653466wfj.204.1230136316698; Wed, 24 Dec 2008 08:31:56 -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 30sm17359824wff.32.2008.12.24.08.31.54 (version=SSLv3 cipher=RC4-MD5); Wed, 24 Dec 2008 08:31:55 -0800 (PST) From: Kevin Kempter Organization: Consistent State To: pgsql-admin@postgresql.org Subject: vacuum monitoring question Date: Wed, 24 Dec 2008 09:31:53 -0700 User-Agent: KMail/1.10.3 (Linux/2.6.27.7-134.fc10.x86_64; KDE/4.1.3; x86_64; ; ) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="Boundary-00=_5PmUJbbWxXW56yB" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200812240931.53278.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/185 X-Sequence-Number: 31018 --Boundary-00=_5PmUJbbWxXW56yB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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.. Thoughts ? Thanks in advance --Boundary-00=_5PmUJbbWxXW56yB Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit

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..

Thoughts ?

Thanks in advance

--Boundary-00=_5PmUJbbWxXW56yB--