| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
| 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 19:38:31 |
| Message-ID: | 4373A1B7.3030005@zeut.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Scott Marlowe wrote:
> 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...
I assumed (perhaps incorrectly) that you were talking about maintaining
the data in the theoretical / not yet in existence autovacuum stats
table through database restart, the stats system already has a GUC var
that dictates whether or not it dumps it's data upon DB restart.
Matt
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Bohmer | 2005-11-10 20:06:37 | Re: autovacuum daemon question... |
| Previous Message | Chris Hoover | 2005-11-10 17:26:50 | Re: Partitioning in 8.1 |