pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Goldner <MGoldner@agmednet.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Is my vacuumdb stuck in a loop?
Date: Sun, 02 Mar 2008 11:15:59 -0500
Message-ID: <20299.1204474559@sss.pgh.pa.us> (raw)
In-Reply-To: <C3F02959.1E4A4%mgoldner@agmednet.com>
References: <C3F02959.1E4A4%mgoldner@agmednet.com>

"Michael Goldner" <MGoldner@agmednet.com> writes:
> Am I stuck in a loop, or is this happening because the size of the relation
> is so large that postgres is operating on smaller chunks?

It's removing as many dead rows at a time as it can handle.  Arithmetic
suggests that you've got maintenance_work_mem set to 64MB, which would
be enough room to process 11184810 rows per index scanning cycle.

The fact that there are so many dead large objects is what I'd be
worrying about.  Does that square with your sense of what you've
removed, or does it suggest you've got a large object leak?  Do you
use contrib/lo and/or contrib/vacuumlo to manage them?

The numbers also suggest that you might be removing all or nearly
all of the rows in pg_largeobject.  If so, a CLUSTER on it might
be more effective than VACUUM as a one-shot cleanup method.

			regards, tom lane



view thread (4+ messages)  latest in thread

Message-ID: <20299.1204474559@sss.pgh.pa.us>
Permalink:  ../20299.1204474559@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/20299.1204474559@sss.pgh.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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, MGoldner@agmednet.com
  Subject: Re: Is my vacuumdb stuck in a loop?
  In-Reply-To: <20299.1204474559@sss.pgh.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