Skip site navigation (1) Skip section navigation (2)

Autovacuum / full vacuum

From: Michael Riess <mlriess(at)gmx(dot)de>
To: pgsql-performance(at)postgresql(dot)org
Subject: Autovacuum / full vacuum
Date: 2006-01-17 10:18:59
Message-ID: dqigaf$1b98$ (view raw, whole thread or download thread mbox)
Lists: pgsql-performance

I'm curious as to why autovacuum is not designed to do full vacuum. I 
know that the necessity of doing full vacuums can be reduced by 
increasing the FSM, but in my opinion that is the wrong decision for 
many applications. My application does not continuously 
insert/update/delete tuples at a constant rate. Basically there are long 
periods of relatively few modifications and short burst of high 
activity. Increasing the FSM so that even during these bursts most space 
  would be reused would mean to reduce the available memory for all 
other database tasks.

So my question is: What's the use of an autovacuum daemon if I still 
have to use a cron job to do full vacuums? wouldn't it just be a minor 
job to enhance autovacuum to be able to perform full vacuums, if one 
really wants it to do that - even if some developers think that it's the 
wrong approach?



pgsql-performance by date

Next:From: Christopher Kings-LynneDate: 2006-01-17 10:29:37
Subject: Re: Autovacuum / full vacuum
Previous:From: MarcosDate: 2006-01-17 09:04:53
Subject: Use of Stored Procedures and

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group