Skip site navigation (1) Skip section navigation (2)

Re: We need to log aborted autovacuums

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: We need to log aborted autovacuums
Date: 2010-11-17 21:55:40
Message-ID: 1290030940.10258.7188.camel@jd-desktop (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, 2010-11-17 at 13:46 -0800, Josh Berkus wrote:
> Hackers,
> 
> I've been trying to diagnose in a production database why certain tables
> never get autovacuumed despite having a substantial % of updates.  The
> obvious reason is locks blocking autovacuum from vacuuming the table ...
> but the trick is we don't log such blocking behavior, at all.  This
> means that there is no possible way for a user to figure out *why* his
> tables aren't getting autovacuumed.

Yes we do log this.

JD

-- 
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt


In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-11-17 22:23:54
Subject: Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running
Previous:From: Josh BerkusDate: 2010-11-17 21:46:21
Subject: We need to log aborted autovacuums

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group