Re: Autovacuum / full vacuum - Mailing list pgsql-performance

From Alvaro Herrera
Subject Re: Autovacuum / full vacuum
Date
Msg-id 20060117173046.GA4296@surnet.cl
Whole thread Raw
In response to Re: Autovacuum / full vacuum  (Chris Browne <cbbrowne@acm.org>)
List pgsql-performance
Chris Browne wrote:
> ajs@crankycanuck.ca (Andrew Sullivan) writes:
> > 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.
>
> That's a bit more than what autovacuum would probably do...
> autovacuum does things table by table, so that what would be locked
> should just be one table.

Even a database-wide vacuum does not take locks on more than one table.
The table locks are acquired and released one by one, as the operation
proceeds.  And as you know, autovacuum (both 8.1's and contrib) does
issue database-wide vacuums, if it finds a database close to an xid
wraparound.

--
Alvaro Herrera                        http://www.advogato.org/person/alvherre
"Las mujeres son como hondas:  mientras más resistencia tienen,
 más lejos puedes llegar con ellas"  (Jonas Nightingale, Leap of Faith)

pgsql-performance by date:

Previous
From: Markus Schaber
Date:
Subject: Re: Autovacuum / full vacuum
Next
From: Scott Marlowe
Date:
Subject: Re: Autovacuum / full vacuum