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

  Tom,

It was not consuming any CPU time. I found that another process on the 
machine failed. That process was trying to write to a different table 
(not the one I was vacuuming) in the database and that table was locked 
(not sure why).  It produced thousands of errors which caused the log 
files to grow large enough that the entire disk was filled, and this 
brought everything to a halt.

So I had to kill my process, recover disk space and get the machine back 
in working condition for the weekend. I guess I will attempt to do the 
full vacuum again next week.

I am still wondering how the vacuum process actually works. When it 
throws the output lines that show how many rows are 
recoverable/nonremovable, does this mean that the vacuum has completed?  
Or do those output lines show the vacuum has scanned through the 
database...found what what it is going to recover and then takes on the 
vacuum process?

Thanks,
Dave

Tom Lane said the following on 7/15/2011 1:12 PM:
> 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

Attachments:

david_ondrejik.vcf (text/x-vcard, 307B) download begin:vcard fn:David Ondrejik n:Ondrejik;David org:weather.gov/marfc;NOAA's National Weather Service adr;dom:Suite #330;;328 Innovation Blvd;State College;PA;16803 email;internet:david.ondrejik@noaa.gov title:Senior Hydrologist. Mid-Atlantic River Forecast Center tel;work:814-231-2401 version:2.1 end:vcard

view thread (13+ messages)  latest in thread

Message-ID: <4E208B57.6010401@noaa.gov>
Permalink:  ../4E208B57.6010401@noaa.gov/
Also on:    postgresql.org/message-id/4E208B57.6010401@noaa.gov

 · 

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: David.Ondrejik@noaa.gov, tgl@sss.pgh.pa.us, simon@2ndQuadrant.com
  Subject: Re: vacuumdb question/problem
  In-Reply-To: <4E208B57.6010401@noaa.gov>

* 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