pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: Steven Flatt <steven.flatt@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Database-wide vacuum can take a long time, duringwhich tables are not being analyzed
Date: Thu, 02 Nov 2006 10:49:18 +0000
Message-ID: <1162464559.3587.291.camel@silverbirch.site> (raw)
In-Reply-To: <357fa7590611011115q748ddce9qa6cf570ec2f15348@mail.gmail.com>
References: <357fa7590611011115q748ddce9qa6cf570ec2f15348@mail.gmail.com>

On Wed, 2006-11-01 at 14:15 -0500, Steven Flatt wrote:
> Here is a potential problem with the auto-vacuum daemon, and I'm
> wondering if anyone has considered this.  To avoid transaction ID
> wraparound, the auto-vacuum daemon will periodically determine that it
> needs to do a DB-wide vacuum, which takes a long time.  On our system,
> it is on the order of a couple of weeks.  (The system is very busy and
> there is a lot of I/O going on pretty much 24/7).  During this period
> of time, there is nothing to automatically analyze any of the tables,
> leading to further performance problems.  What are your thoughts on
> having the DB-wide vacuum running on a separate thread so that the
> daemon can concurrently wake up and take care of analyzing tables?

Yes, do it.

Every couple of weeks implies a transaction rate of ~~500tps, so I'd be
interested to hear more about your system. 

-- 
  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com





view thread (5+ messages)  latest in thread

Message-ID: <1162464559.3587.291.camel@silverbirch.site>
Permalink:  ../1162464559.3587.291.camel@silverbirch.site/
Also on:    postgresql.org/message-id/1162464559.3587.291.camel@silverbirch.site

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: simon@2ndquadrant.com, steven.flatt@gmail.com
  Subject: Re: Database-wide vacuum can take a long time, duringwhich tables are not being analyzed
  In-Reply-To: <1162464559.3587.291.camel@silverbirch.site>

* 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