pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Jeff Bohmer <jdblist@visionlink.org>
Cc: Matthew T. O'Connor <matthew@zeut.net>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Joe Maldonado <joe.maldonado@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: autovacuum daemon question...
Date: Sat, 3 Dec 2005 23:03:05 -0500 (EST)
Message-ID: <200512040403.jB4435Z09628@candle.pha.pa.us> (raw)
In-Reply-To: <p06230900bf9961d37627@[192.168.1.200]>


Added to TODO for autovacuum:

        o Consider logging activity either to the logs or a system view


---------------------------------------------------------------------------

Jeff Bohmer wrote:
> 
> >>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.
> >
> >I'm confused...  the GUC var stats_reset_on_server_start dictates if 
> >the stats system dumps its data on DB restart.  If we added a new 
> >table to the stats system kept track of autovacuum activity, then 
> >that data would also be dumped on restart if 
> >stats_reset_on_server_start=true.
> 
> 
> Yep.  I was thinking of a way to muck up the stats system by keeping 
> autovacuum's VACUUM activity irregardless of 
> stats_reset_on_server_start.  Because autovacuum's VACUUM activity 
> data would be relevant across restarts, even if 
> stats_reset_on_server_start=true.  But I see now that my idea is ugly 
> and just confuses things.  I agree that having it work the way you 
> suggest is preferable.
> 
> - Jeff
> 
> 
> -- 
> 
> Jeff Bohmer
> VisionLink, Inc.
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (16+ messages)

Message-ID: <200512040403.jB4435Z09628@candle.pha.pa.us>
Permalink:  ../200512040403.jB4435Z09628@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200512040403.jB4435Z09628@candle.pha.pa.us

 · 

reply

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: pgman@candle.pha.pa.us, jdblist@visionlink.org, matthew@zeut.net, smarlowe@g2switchworks.com, joe.maldonado@gmail.com
  Subject: Re: autovacuum daemon question...
  In-Reply-To: <200512040403.jB4435Z09628@candle.pha.pa.us>
  References: <p06230900bf9961d37627@[192.168.1.200]> <200512040403.jB4435Z09628@candle.pha.pa.us>

* 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