X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id C91A811F61BA for ; Fri, 14 Apr 2006 20:33:44 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 0.06 X-Spam-Level: X-Spam-Status: No, score=0.06 required=5 tests=[AWL=0.060] Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id sy5kvKT5c5hL for ; Fri, 14 Apr 2006 20:33:38 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.clickspace.com (router2.clickspace.com [65.110.166.227]) by postgresql.org (Postfix) with ESMTP id A8E2911F6936 for ; Fri, 14 Apr 2006 20:33:41 -0300 (ADT) Received: from [10.0.1.4] ([68.147.204.179]) (authenticated user brendan@clickspace.com) by mail.clickspace.com (using TLSv1/SSLv3 with cipher RC4-SHA (128 bits)); Fri, 14 Apr 2006 17:33:40 -0600 In-Reply-To: <443DFF8B.1010103@edesix.com> References: <1d219a6f0604111602m62445e60h425c5dd59219606e@mail.gmail.com> <443C39ED.6050706@aurema.com> <1d219a6f0604120753h1cabb4c2n60f53403225dcf81@mail.gmail.com> <20060412151553.GD23855@surnet.cl> <1d219a6f0604121353t1e997628i6e10d00bed4b2354@mail.gmail.com> <443DFF8B.1010103@edesix.com> Mime-Version: 1.0 (Apple Message framework v749.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: "pgsql-admin@postgresql.org" Content-Transfer-Encoding: 7bit From: Brendan Duddridge Subject: Re: Autovacuum ideas Date: Fri, 14 Apr 2006 17:33:28 -0600 To: Robin Iddon X-Mailer: Apple Mail (2.749.3) X-Archive-Number: 200604/134 X-Sequence-Number: 21303 I guess I was thinking that if you do a vacuum analyze verbose from within psql, it does vacuum the big 'insert only' tables. Of course it never finds any dead rows, but it does take a long time to get past those tables. I didn't know that autovacuum would be any different. ____________________________________________________________________ Brendan Duddridge | CTO | 403-277-5591 x24 | brendan@clickspace.com ClickSpace Interactive Inc. Suite L100, 239 - 10th Ave. SE Calgary, AB T2G 0V9 http://www.clickspace.com On Apr 13, 2006, at 1:36 AM, Robin Iddon wrote: > Brendan Duddridge wrote: >> What I'd like to see is a table exclusion list. I have a few very >> large history tables that are never updated or deleted, only >> inserts and selects. > > Such a table will never trigger the vacuum rules as I understand > them (vacuum only happens on table that have obsolete tuples, which > means update or delete). > > It will correctly trigger the analyze rules now and then, but > analyze is cheap compared to vacuum and is desirable because it > will help the planner do it's job (assuming that querying the table > is important to you). Remember analyze only requires a read-lock > on the table so it can run in parallel with other queries quite > happily. > > If you really need to disable autovac on a table you can disable > pg_autovacuum from running on a specific table by creating a row > for your table in pg_autovacuum table and setting the > pg_autovacuum.enabled to false. > > > > Robin > > > ---------------------------(end of > broadcast)--------------------------- > TIP 6: explain analyze is your friend >