| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
| Cc: | 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:11:15 |
| Message-ID: | 200608171711.k7HHBFP16765@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Matthew T. O'Connor wrote:
> Bruce Momjian wrote:
> > Matthew T. O'Connor wrote:
> >
> >> and increasing the log level when autovacuum actually fires off a VACUUM
> >> or ANALYZE command.
> >>
> >
> > This was not done because the logging control only for autovacuum was
> > going to be added. Right now, if you want to see the vacuum activity,
> > you end up seeing debug stuff too (very ugly).
>
> 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.
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-08-17 17:11:45 | Re: Enum proposal / design |
| Previous Message | Chris Mair | 2006-08-17 17:10:25 | Re: [HACKERS] selecting large result sets in psql using |