Re: CPU-intensive autovacuuming - Mailing list pgsql-general

From Phil Endecott
Subject Re: CPU-intensive autovacuuming
Date
Msg-id 42A5BEC3.4080409@chezphil.org
Whole thread Raw
In response to Re: CPU-intensive autovacuuming  ("Matthew T. O'Connor" <matthew@zeut.net>)
Responses Re: CPU-intensive autovacuuming
Re: CPU-intensive autovacuuming
Re: CPU-intensive autovacuuming
List pgsql-general
Matthew T. O'Connor wrote:
> The integrated version
> of autovacuum that didn't make the cut before 8.0 avoids this problem
> since the autovacuum data is stored in the database.

What is the status of this?  Is it something that will be included in
8.1 or 8.0.n?  I might be able to patch the current code but that
doesn't seem like a useful thing to do if a better solution will arrive
eventually.  I am currently running vacuums from a cron job and I think
I will be happy with that for the time being.

(Incidentally, I have also found that the indexes on my pg_attributes
table were taking up over half a gigabyte, which came down to less than
40 megs after reindexing them.  Is there a case for having autovacuum
also call reindex?)

--Phil.


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Update sql question
Next
From: "Thomas Radnetter"
Date:
Subject: how to loop until eof in a cursor with pgsql