pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndQuadrant.com>
Cc: David Ondrejik <David.Ondrejik@noaa.gov>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: vacuumdb question/problem
Date: Fri, 15 Jul 2011 13:12:47 -0400
Message-ID: <3239.1310749967@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+U5nMLRcZRceB9FMeJBJN3fPyqNeGmEapzSXS3h=omPyntJeg@mail.gmail.com>
References: <4E206658.4040600@noaa.gov>
	<CA+U5nMLRcZRceB9FMeJBJN3fPyqNeGmEapzSXS3h=omPyntJeg@mail.gmail.com>

Simon Riggs <simon@2ndQuadrant.com> writes:
> On Fri, Jul 15, 2011 at 5:10 PM, David Ondrejik <David.Ondrejik@noaa.gov> wrote:
>> Since then, the process has continued to run (for about 20 hrs) without any
>> additional information being returned.

> Probably locked behind another long running task that is holding a buffer pin.

That's possible, or it could be busy vacuuming some (really large?)
index.  Is the process actually busy, as in consuming CPU time according
to top or other process monitoring tool?

			regards, tom lane



view thread (13+ messages)  latest in thread

Message-ID: <3239.1310749967@sss.pgh.pa.us>
Permalink:  ../3239.1310749967@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3239.1310749967@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, simon@2ndQuadrant.com, David.Ondrejik@noaa.gov
  Subject: Re: vacuumdb question/problem
  In-Reply-To: <3239.1310749967@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