From: Robin Iddon <robin@edesix.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Autovacuum ideas
Date: Thu, 13 Apr 2006 08:36:43 +0100
Message-ID: <443DFF8B.1010103@edesix.com> (raw)
In-Reply-To: <F8AC66B7-3E32-4DE3-BC25-E2AB5B341600@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>
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
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: robin@edesix.com
Subject: Re: Autovacuum ideas
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>
* 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