pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Brendan Duddridge <brendan@clickspace.com>
To: Robin Iddon <robin@edesix.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Autovacuum ideas
Date: Fri, 14 Apr 2006 17:33:28 -0600
Message-ID: <BFE1A0A4-146E-453A-AFFC-19DB1C237D81@clickspace.com> (raw)
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>
	<F8AC66B7-3E32-4DE3-BC25-E2AB5B341600@clickspace.com>
	<443DFF8B.1010103@edesix.com>

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
>





view thread (14+ messages)  latest in thread

Message-ID: <BFE1A0A4-146E-453A-AFFC-19DB1C237D81@clickspace.com>
Permalink:  ../BFE1A0A4-146E-453A-AFFC-19DB1C237D81@clickspace.com/
Also on:    postgresql.org/message-id/BFE1A0A4-146E-453A-AFFC-19DB1C237D81@clickspace.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: brendan@clickspace.com, robin@edesix.com
  Subject: Re: Autovacuum ideas
  In-Reply-To: <BFE1A0A4-146E-453A-AFFC-19DB1C237D81@clickspace.com>
  References: <1d219a6f0604111602m62445e60h425c5dd59219606e@mail.gmail.com> <443C39ED.6050706@aurema.com> <1d219a6f0604120753h1cabb4c2n60f53403225dcf81@mail.gmail.com> <20060412151553.GD23855@surnet.cl> <1d219a6f0604121353t1e997628i6e10d00bed4b2354@mail.gmail.com> <F8AC66B7-3E32-4DE3-BC25-E2AB5B341600@clickspace.com> <443DFF8B.1010103@edesix.com> <BFE1A0A4-146E-453A-AFFC-19DB1C237D81@clickspace.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