Re: Autovacuum ideas - Mailing list pgsql-admin

From Robin Iddon
Subject Re: Autovacuum ideas
Date
Msg-id 443DFF8B.1010103@edesix.com
Whole thread Raw
In response to Re: Autovacuum ideas  (Brendan Duddridge <brendan@clickspace.com>)
Responses Re: Autovacuum ideas  (Brendan Duddridge <brendan@clickspace.com>)
List pgsql-admin
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


pgsql-admin by date:

Previous
From: Grega Bremec
Date:
Subject: Re: FW: Setting up of PITR system.
Next
From: "Rajesh Kumar Mallah"
Date:
Subject: Re: FW: Setting up of PITR system.