Re: Autovacuum in the backend - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Autovacuum in the backend
Date
Msg-id 42B275BE.1000701@commandprompt.com
Whole thread Raw
In response to Re: Autovacuum in the backend  ("Matthew T. O'Connor" <matthew@zeut.net>)
Responses Re: Autovacuum in the backend
Re: Autovacuum in the backend
Re: Autovacuum in the backend
Re: Autovacuum in the backend
Re: Autovacuum in the backend
List pgsql-hackers
Matthew T. O'Connor wrote:
> Joshua D. Drake wrote:
> 
>> Just my own two cents. First I am not knocking the work that has been 
>> on autovacuum. I am sure that it was a leap on its own to get it to 
>> work. However I will say that I just don't see the reason for it.
> 
> 
> 
> The major reasons for autovacuum as I see it are as follows:
> 
> * Reduces administrative overhead having to keep track of what tables 
> need to be vacuumed how often.

Creates more overhead and thus reduces performance.


> * Reduces the total amount of time the system spends vacuuming since it 
> only vacuums when needed.

Can be easily done with cron.

> * Keeps stats up-to-date automatically

Which can be done with cron

> * Eliminates newbie confusion

RTFM

> * Eliminates one of the criticisms that the public has against 
> PostgreSQL (justifed or not)

Agreed.


Just so everyone knows from the get go here. I am purposely playing a 
little devils advocate. Autovacuum has some drawbacks. I think we should
be **publicly** aware of them before we pursue integration.

Heaven knows it would make my life easier if it was integrated but anyway...

Sincerely,

Joshua D. Drake




> 
> Also, as VACUUM improves, autovacuum will improve with it.
> 



pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Autovacuum in the backend
Next
From: Hans-Jürgen Schönig
Date:
Subject: Re: Autovacuum in the backend