pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-admin@postgresql.org
Subject: Re: Vacuum Problems (locking)
Date: Thu, 26 Oct 2006 07:03:09 -0400
Message-ID: <20061026110309.GB4083@phlogiston.dyndns.org> (raw)
In-Reply-To: <1161806057.2095.154.camel@localhost.localdomain>
References: <1161806057.2095.154.camel@localhost.localdomain>

On Wed, Oct 25, 2006 at 03:54:17PM -0400, Mike Goldner wrote:
> Finally, and most important is the blocking.  The vacuum duration
> reported in the log converts to about 170 minutes.  I can track
> backwards in the log and the only messages prior to the 6:52am
> completion of the vacuum end at 3:57am (almost exactly 170 minutes
> prior).
> 
> So, all indications point to postgres blocking all access during the
> entire vacuum.  

The vacuum command you posted doesn't block.  I can think of two
other explanations:

1.	You just didn't have any activity then.  Don't throw away
this possibility without evidence: I can't count the number of blind
alleys I've been down because someone insisted that "never happens".

2.	You're completely pegged on I/O.  Vacuum will make this
worse, and maybe therefore no transactions get through.  You can
fiddle with the vacuum settings to get them to back off a little and
let some other transactions through. 

That said, your essential problem is that one table.  Vacuum it more
often -- from the look of the churn on it, I'd just put a job on it
that runs all the time and sleeps for a few seconds in between -- and
you shouldn't have this problem.  But you'll need to VACUUM FULL or
dump and reload first.

A

-- 
Andrew Sullivan  | ajs@crankycanuck.ca
Windows is a platform without soap, where rats run around 
in open sewers.
		--Daniel Eran



view thread (6+ messages)  latest in thread

Message-ID: <20061026110309.GB4083@phlogiston.dyndns.org>
Permalink:  ../20061026110309.GB4083@phlogiston.dyndns.org/
Also on:    postgresql.org/message-id/20061026110309.GB4083@phlogiston.dyndns.org

 · 

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: ajs@crankycanuck.ca
  Subject: Re: Vacuum Problems (locking)
  In-Reply-To: <20061026110309.GB4083@phlogiston.dyndns.org>
  References: <1161806057.2095.154.camel@localhost.localdomain> <20061026110309.GB4083@phlogiston.dyndns.org>

* 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