Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id AD09264FE81 for ; Wed, 24 Dec 2008 12:56:32 -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 43671-04 for ; Wed, 24 Dec 2008 12:56:30 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.230]) by mail.postgresql.org (Postfix) with ESMTP id 06F8F64FD3D for ; Wed, 24 Dec 2008 12:56:29 -0400 (AST) Received: by rv-out-0506.google.com with SMTP id b25so4430656rvf.43 for ; Wed, 24 Dec 2008 08:56:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=5EAL9dLbugnRwk58xOQOEqrNdQ1OwTrUdrhzrI/1UBQ=; b=DNjGEB7AkOrDfOD6fhlMn2cLCi7X54oKrUMJvsC+AGuTXrrHC+ipx/pOHZgEKJv88l Zqnx7loLw+Q2PhwYOEZNyH95BRwWMFlIcKeVQwzOV+be695A6LBkLo0a4RiVtYfVDYVa peKQy3CO4q5AwOE0uu8sTCjw3dPHIXAAphYT0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=UqJy6M43sCx/HSkfv15D/7JGFIeF/UwlhU7soKCvy5eiAhtCjuQO/SLv+UfCnDs88d PH2hNiaGgMvApdStOwvfJVnDX4CvzLgh4CdD7fl+KVEoop38j6gcQSeDaEjhhELg9BxC ZIsieKjYjxsAIk5wUbkNmqKhWJ8tmmpS2Vdq4= Received: by 10.114.177.1 with SMTP id z1mr5643828wae.68.1230137789124; Wed, 24 Dec 2008 08:56:29 -0800 (PST) Received: by 10.114.132.17 with HTTP; Wed, 24 Dec 2008 08:56:29 -0800 (PST) Message-ID: Date: Wed, 24 Dec 2008 09:56:29 -0700 From: "Scott Marlowe" To: "Kevin Kempter" Subject: Re: vacuum monitoring question Cc: pgsql-admin@postgresql.org In-Reply-To: <200812240931.53278.kevink@consistentstate.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200812240931.53278.kevink@consistentstate.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200812/186 X-Sequence-Number: 31019 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.