From: | Darcy Buskermolen <darcy(at)ok-connect(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 15:16:43 |
Message-ID: | 200701160716.44168.darcy@ok-connect.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Tuesday 16 January 2007 06:29, Alvaro Herrera wrote:
> 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.
Yes I did intend this thought for vacuum, not strictly autovacuum.
From | Date | Subject | |
---|---|---|---|
Next Message | Jasbinder Singh Bali | 2007-01-16 15:25:56 | Re: Dynamic loading of Perl Code in Postgres functions |
Previous Message | Oisin Glynn | 2007-01-16 15:12:46 | Re: NOTIFY QUESTION |
From | Date | Subject | |
---|---|---|---|
Next Message | Darcy Buskermolen | 2007-01-16 15:30:41 | Re: Autovacuum improvements |
Previous Message | Alvaro Herrera | 2007-01-16 15:03:57 | Re: Enabling autovacuum by default (was Re: Autovacuum |