| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Pavan Deolasee <pavan(at)enterprisedb(dot)com>, Christopher Browne <cbbrowne(at)acm(dot)org>, pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Autovacuum Improvements |
| Date: | 2007-01-16 14:29:18 |
| Message-ID: | 20070116142918.GX24671@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
elein wrote:
> Have you made any consideration of providing feedback on autovacuum to users?
> Right now we don't even know what tables were vacuumed when and what was
> reaped. This might actually be another topic.
I'd like to hear other people's opinions on Darcy Buskermolen proposal
to have a log table, on which we'd register what did we run, at what
time, how long did it last, how many tuples did it clean, etc. I feel
having it on the regular text log is useful but it's not good enough.
Keep in mind that in the future we may want to peek at that collected
information to be able to take better scheduling decisions (or at least
inform the DBA that he sucks).
Now, I'd like this to be a VACUUM thing, not autovacuum. That means
that manually-run vacuums would be logged as well.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John DeSoi | 2007-01-16 14:39:10 | Re: Dynamic loading of Perl Code in Postgres functions |
| Previous Message | Alvaro Herrera | 2007-01-16 14:25:25 | Re: Autovacuum Improvements |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-01-16 15:03:57 | Re: Enabling autovacuum by default (was Re: Autovacuum |
| Previous Message | Andrew Dunstan | 2007-01-16 14:27:53 | Re: Enabling autovacuum by default (was Re: Autovacuum |