From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Autovacuum on by default? |
Date: | 2006-08-17 17:38:33 |
Message-ID: | 20060817173833.GT318@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Matthew T. O'Connor wrote:
> Bruce Momjian wrote:
> >Matthew T. O'Connor wrote:
> >
> >>Any chance we can make this change before release? I think it's very
> >>important to be able to look through the logs and *know* that you tables
> >>are getting vacuumed or not.
> >>
> >
> >Agreed. I just IM'ed Alvaro and he says pg_stat_activity should now
> >show exactly what autovacuum is doing (and if it doesn't, let's fix it).
> >I think that is the best solution to the monitoring problem, rather than
> >throwing lines in the server logs.
>
> I'm not sure I agree with this. I can use the pg_stat_activity table to
> see if autovacuum is doing something right now, but what I want to be
> able to do is look through my logs and see that table_foo hasn't been
> vacuumed since last week, or that table_bar has been vacuumed 7 times
> today. Can I do that just with the stat system alone?
Actually Larry just reminded us that you can use pg_stat_all_tables to
see that information. However I'm testing it and it doesn't seem to
work for all tables ... strange. I'll have a look.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew T. O'Connor | 2006-08-17 17:40:41 | Re: Autovacuum on by default? |
Previous Message | Bruce Momjian | 2006-08-17 17:36:23 | Re: Autovacuum on by default? |