From: Jeff Bohmer <jdblist@visionlink.org>
To: Matthew T. O'Connor <matthew@zeut.net>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Jeff Bohmer <jdblist@visionlink.org>
Cc: Joe Maldonado <joe.maldonado@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: autovacuum daemon question...
Date: Thu, 10 Nov 2005 13:06:37 -0700
Message-ID: <p06230910bf9953c7c839@[192.168.1.200]> (raw)
In-Reply-To: <4373A1B7.3030005@zeut.net>
References: <824355640511090720l27eabde8r61573e574f4904ab@mail.gmail.com>
<437227FA.9020502@tocr.com>
<824355640511091134t7123bb51sf759391f68c1590f@mail.gmail.com>
<19439.1131571556@sss.pgh.pa.us>
<43727C5E.7090501@zeut.net>
<p06230907bf98ad60e3f2@[192.168.1.200]>
<1131635881.3554.60.camel@state.g2switchworks.com>
<43736D98.5060205@zeut.net>
<1131638596.3554.77.camel@state.g2switchworks.com>
<4373A1B7.3030005@zeut.net>
>>>>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
AFAIK, a restart does not affect the VACUUMed-ness of anything.
Keeping these (currently nonexistent autovacuum) stats across
restarts would be helpful if stats_reset_on_server_start=on.
Unless I misunderstand, if stats_reset_on_server_start=off, these
(currently nonexistent autovacuum) stats would only be relevant for
autovacuum's VACUUM activity and not it's ANALYZE activity. In which
case, it seems ideal to keep autovacuum VACUUM stats regardless of
the GUC setting, while autovacuum ANALYZE stats should follow it.
But if the ideal is impractical, making both ANALYZE and VACUUM stats
follow the GUC would still be real nice.
- Jeff
--
Jeff Bohmer
VisionLink, Inc.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: jdblist@visionlink.org, matthew@zeut.net, smarlowe@g2switchworks.com, joe.maldonado@gmail.com
Subject: Re: autovacuum daemon question...
In-Reply-To: <p06230910bf9953c7c839@[192.168.1.200]>
References: <824355640511090720l27eabde8r61573e574f4904ab@mail.gmail.com> <437227FA.9020502@tocr.com> <824355640511091134t7123bb51sf759391f68c1590f@mail.gmail.com> <19439.1131571556@sss.pgh.pa.us> <43727C5E.7090501@zeut.net> <p06230907bf98ad60e3f2@[192.168.1.200]> <1131635881.3554.60.camel@state.g2switchworks.com> <43736D98.5060205@zeut.net> <1131638596.3554.77.camel@state.g2switchworks.com> <4373A1B7.3030005@zeut.net> <p06230910bf9953c7c839@[192.168.1.200]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox