Re: VACUUM FULL ANALYSE hanging

From: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
To: Gabriele Bartolini <g(dot)bartolini(at)comune(dot)prato(dot)it>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: VACUUM FULL ANALYSE hanging
Date: 2007-05-02 15:40:59
Message-ID: 1178120459.2953.16.camel@state.g2switchworks.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wed, 2007-05-02 at 05:05, Gabriele Bartolini wrote:
> Hi guys,
>
> I am having problems with freeing disk space after a massive delete
> operation on a table that had approximately 80 million record. I
> ran the following command, by setting the vacuum memory to
> approximately a GigaByte:
>
> SET vacuum_mem TO 1024000
> VACUUM FULL ANALYSE VERBOSE oltp.requests
>
> Here is what I get:

SNIP

> DETAIL: 8211835 index row versions were removed.
> 73821 index pages have been deleted, 73821 are currently reusable.
> CPU 17.06s/28.14u sec elapsed 319.16 sec.
>
> But here, the command simply hangs.
>
> The table description is:

Maybe it's hanging, maybe it's just taking a really long time to finish
and get back to you.

What's vmstat / top /iostat got to say about the machine during this
"hang"?

IF the I/O or CPU are high, then it's not hung, it's just taking a
while.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message dx k9 2007-05-02 15:49:14 Re: reindexdb hangs
Previous Message Scott Marlowe 2007-05-02 15:39:29 Re: infinite blocking statements in 8.2.3