Message-ID: <4EE61AB8.1010202@enterprisedb.com>
Date: Mon, 12 Dec 2011 17:16:08 +0200
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; fi-FI;
	rv:1.9.2.24) Gecko/20111114 Icedove/3.1.16
MIME-Version: 1.0
To: Anibal David Acosta <aa@devshock.com>
CC: pgsql-performance@postgresql.org
Subject: Re: autovacuum, exclude table
References: <00f501ccb8d9$f07dc4d0$d1794e70$@devshock.com>
In-Reply-To: <00f501ccb8d9$f07dc4d0$d1794e70$@devshock.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 12.12.2011 16:25, Anibal David Acosta wrote:
> I have a couple of tables with about 400millions of records increasing about
> 5 millions per day.
>
> I think that disabling autovac over those tables, and enabling daily manual
> vacuum (in some idle hour) will be better.
>
> I am right?

Possibly. If the system is otherwise idle, it sounds sensible to do 
routine maintenance at that time.

> Is possible to exclude autovacuum over some tables?

Sure, see 
http://www.postgresql.org/docs/9.1/static/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS

ALTER TABLE foo SET (autovacuum_enabled=false, toast.autovacuum_enabled 
= false);

It might be better, though, to let autovacuum enabled, and just do the 
additional manual VACUUM in the idle period. If the daily manual VACUUM 
is enough to keep the bloat within the autovacuum thresholds, autovacuum 
will never kick in. If it's not enough, then you probably want 
autovacuum to run.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com