From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
Cc: | Jeff Bohmer <jdblist(at)visionlink(dot)org>, Joe Maldonado <joe(dot)maldonado(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: autovacuum daemon question... |
Date: | 2005-11-10 16:03:17 |
Message-ID: | 1131638596.3554.77.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thu, 2005-11-10 at 09:56, Matthew T. O'Connor wrote:
> Scott Marlowe wrote:
> >> I would appreciate an easy way to keep tabs on autovacuum's activity.
> >> A stat table seems like a practical way to have this info readily
> >> available.
> >>
> >> No need to keep values across dump/reloads, right?
> >>
> >
> > This sounds more and more like a good idea. I don't think there's any
> > need to maintain across dump/reload and / or database restart either.
>
> The DBA can elect to keep or discard stats data across DB restart, in
> fact I think the default value for this GUC var was set to true for the
> 8.1 release.
I thought we were discussing a theoretical / not yet in existence GUC
var...
From | Date | Subject | |
---|---|---|---|
Next Message | CG | 2005-11-10 16:30:02 | ClusterDB error message |
Previous Message | Matthew T. O'Connor | 2005-11-10 15:56:08 | Re: autovacuum daemon question... |