Re: Autovacuum / full vacuum

From: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Autovacuum / full vacuum
Date: 2006-01-17 14:56:49
Message-ID: 20060117145649.GE21092@phlogiston.dyndns.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Jan 17, 2006 at 11:18:59AM +0100, Michael Riess wrote:
> hi,
>
> I'm curious as to why autovacuum is not designed to do full vacuum. I

Because nothing that runs automatically should ever take an exclusive
lock on the entire database, which is what VACUUM FULL does.

> 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.

I don't believe the hit is enough that you should even notice it.
You'd have to post some pretty incredible use cases to show that the
tiny loss of memory to FSM is worth (a) an exclusive lock and (b) the
loss of efficiency you get from having some preallocated pages in
tables.

A

--
Andrew Sullivan | ajs(at)crankycanuck(dot)ca
The fact that technology doesn't work is no bar to success in the marketplace.
--Philip Greenspun

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Michael Riess 2006-01-17 15:04:41 Re: Autovacuum / full vacuum
Previous Message Michael Riess 2006-01-17 14:50:38 Re: Autovacuum / full vacuum