| From: | Phil Endecott <spam_from_postgresql_general(at)chezphil(dot)org> |
|---|---|
| To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: CPU-intensive autovacuuming |
| Date: | 2005-06-07 15:35:31 |
| Message-ID: | 42A5BEC3.4080409@chezphil.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Radnetter | 2005-06-07 15:40:08 | how to loop until eof in a cursor with pgsql |
| Previous Message | Tom Lane | 2005-06-07 15:30:39 | Re: Update sql question |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew T. O'Connor | 2005-06-07 16:00:54 | Re: CPU-intensive autovacuuming |
| Previous Message | Matthew T. O'Connor | 2005-06-07 15:16:06 | Re: CPU-intensive autovacuuming |