Re: Vaccuum best practice: cronjob or autovaccuum?

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Bill Moran <wmoran(at)collaborativefusion(dot)com>
Cc: Joao Ferreira gmail <joao(dot)miguel(dot)c(dot)ferreira(at)gmail(dot)com>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: Vaccuum best practice: cronjob or autovaccuum?
Date: 2008-08-28 15:48:00
Message-ID: 20080828154800.GC8424@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

For the record:

Bill Moran escribió:

> The naptime at 600 is probably a bad idea. If you only have one user
> database on this system, then it only gets investigated by autovac once
> every 40 minutes (template0 ... template1 ... postgres ... yourdb)
> Consider that autovac uses very little resources when it determines that
> it has no work to do.

Note that on 8.3, the meaning of naptime has changed -- it would be
effectively "check each database once every 10 minutes" if set at 600.
This was changed precisely because the previous semantics were difficult
to explain/use.

The OP is using 8.2 though so it doesn't apply here.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alan Hodgson 2008-08-28 15:54:54 Re: Partitioned Tables - How/Can does slony handle it?
Previous Message Tom Lane 2008-08-28 15:43:31 Re: pg_dumpall problem when roles have default schemas