pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Benjamin Krajmalnik <kraj@illumen.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-admin@postgresql.org
Subject: Re: Autovacuum stopped running
Date: Sat, 1 May 2010 17:21:49 -0600
Message-ID: <F4E6A2751A2823418A21D4A160B68988614362@fletch.stackdump.local> (raw)
In-Reply-To: <11024.1272755375@sss.pgh.pa.us>
References: <F4E6A2751A2823418A21D4A160B6898861435B@fletch.stackdump.local>
	<4BDBF3C90200002500031147@gw.wicourts.gov>
	<F4E6A2751A2823418A21D4A160B6898861435F@fletch.stackdump.local>
	<11024.1272755375@sss.pgh.pa.us>

# - Cost-Based Vacuum Delay -

#vacuum_cost_delay = 0ms		# 0-100 milliseconds
#vacuum_cost_page_hit = 1		# 0-10000 credits
#vacuum_cost_page_miss = 10		# 0-10000 credits
#vacuum_cost_page_dirty = 20		# 0-10000 credits
vacuum_cost_limit = 10000		# 1-10000 credits

#-----------------------------------------------------------------------
-------
# AUTOVACUUM PARAMETERS
#-----------------------------------------------------------------------
-------

#autovacuum = on			# Enable autovacuum subprocess?
'on' 
					# requires track_counts to also
be on.
#log_autovacuum_min_duration = -1	# -1 disables, 0 logs all
actions and
					# their durations, > 0 logs only
					# actions running at least this
number
					# of milliseconds.
autovacuum_max_workers = 10		# max number of autovacuum
subprocesses
#autovacuum_naptime = 1min		# time between autovacuum runs
#autovacuum_vacuum_threshold = 50	# min number of row updates
before
					# vacuum
#autovacuum_analyze_threshold = 50	# min number of row updates
before 
					# analyze
#autovacuum_vacuum_scale_factor = 0.2	# fraction of table size before
vacuum
#autovacuum_analyze_scale_factor = 0.1	# fraction of table size before
analyze
#autovacuum_freeze_max_age = 200000000	# maximum XID age before forced
vacuum
					# (change requires restart)
#autovacuum_vacuum_cost_delay = 20ms	# default vacuum cost delay for
					# autovacuum, in milliseconds;
					# -1 means use vacuum_cost_delay
#autovacuum_vacuum_cost_limit = -1	# default vacuum cost limit for
					# autovacuum, -1 means use
					# vacuum_cost_limit


> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Saturday, May 01, 2010 5:10 PM
> To: Benjamin Krajmalnik
> Cc: Kevin Grittner; pgsql-admin@postgresql.org
> Subject: Re: [ADMIN] Autovacuum stopped running
> 
> "Benjamin Krajmalnik" <kraj@illumen.com> writes:
> > TO be truthful, I did not check that.
> > I arrived at the conclusion because although I have 10 autovacuum
> > threads, none of the tables had been autoanalyzed or autovacuumed in
> > hours (and due to the nature of the activity they do so every
> minute).
> > If I ever see this behavior now I know what to check for :) Thx.
> 
> We've seen one or two previous reports that suggested that the autovac
> launcher might have stopped launching workers, but it hasn't been
> reproducible.  Are you using any nonstandard parameters for
autovacuum?
> 
> 			regards, tom lane



view thread (13+ messages)  latest in thread

Message-ID: <F4E6A2751A2823418A21D4A160B68988614362@fletch.stackdump.local>
Permalink:  ../F4E6A2751A2823418A21D4A160B68988614362@fletch.stackdump.local/
Also on:    postgresql.org/message-id/F4E6A2751A2823418A21D4A160B68988614362@fletch.stackdump.local

 · 

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: kraj@illumen.com, tgl@sss.pgh.pa.us, Kevin.Grittner@wicourts.gov
  Subject: Re: Autovacuum stopped running
  In-Reply-To: <F4E6A2751A2823418A21D4A160B68988614362@fletch.stackdump.local>
  References: <F4E6A2751A2823418A21D4A160B6898861435B@fletch.stackdump.local> <4BDBF3C90200002500031147@gw.wicourts.gov> <F4E6A2751A2823418A21D4A160B6898861435F@fletch.stackdump.local> <11024.1272755375@sss.pgh.pa.us> <F4E6A2751A2823418A21D4A160B68988614362@fletch.stackdump.local>

* 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