Re: pg_autovacuum next steps

From: "Alex J(dot) Avriette" <alex(at)posixnap(dot)net>
To: "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_autovacuum next steps
Date: 2004-03-23 02:50:25
Message-ID: 20040323025025.GK25451@posixnap.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 22, 2004 at 04:50:57PM -0500, Matthew T. O'Connor wrote:

> Could you please explain this better, I don't really understand what the
> problem is. If you want pg_autovacuum to perform a vacuum on a table
> that has had exactly X updates no matter what, you can just run it with
> -V0 -vX (where X is the vacuum threshold) same thing can be done for
> analyze. Are you saying that you did this and it did not work as expected?

My experience was it did not vacuum at all.

> Everyone agrees it should be in the backend eventually the questions
> were just if it was ready, and how or if it should change when it goes in.

It is very simple code, I'm not sure what is "not ready" about it. If
people don't want to use it, they don't have to. Many databases can go
days to weeks without vacuuming.

alex

--
alex(at)posixnap(dot)net
Alex J. Avriette, Unix Systems Gladiator
"You cannot invade the mainland United States. There would be a rifle behind each blade of grass." - Admiral Isoroku Yamamoto

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2004-03-23 02:58:46 bug in 7.4 SET WITHOUT OIDs
Previous Message Matthew T. O'Connor 2004-03-23 02:49:22 Re: [DEFAULT] Daily digest v1.4346 (20 messages)