From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Lonni J Friedman <netllama(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: vacuum process is hanging |
Date: | 2010-06-09 17:27:41 |
Message-ID: | AANLkTimEgQZ71gicV1Z-lOXfNrNAJkDbIzj8XfkTEoWE@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Jun 9, 2010 at 10:13 AM, Lonni J Friedman <netllama(at)gmail(dot)com> wrote:
> Greetings,
> I've got an 8.1.10 instance running on Linux-i686. The system hosts 5
> databases, all of which get vacuumed via a cronjob 3 times a day. All
> of a sudden, the vacuum job for 1 of the databases is hanging
> indefinitely. It normally finishes in under 5 minutes. There are no
> errors in the output, it just stops producing any output. The command
> that I'm running is "vacuumdb -v -z -f -d inventory". I also tried
> removing the -z and -f options to see if that would at least get it to
> complete, but that had no impact. Here's the tail end of the output,
> leading up to the hang:
Well, -f isn't highly recommended anyway, and if you have to do it you
probably need to schedule a reindex to run after it.
Anyway, what does top say about the pg process running the vacuum?
From | Date | Subject | |
---|---|---|---|
Next Message | Geoffrey | 2010-06-09 19:02:07 | calculating distance between longitude and latitude |
Previous Message | Janning | 2010-06-09 16:53:23 | checkpoint spikes |