From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Gabriele Bartolini <g.bartolini@comune.prato.it>
Cc: pgsql-admin@postgresql.org
Subject: Re: VACUUM FULL ANALYSE hanging
Date: Wed, 02 May 2007 10:40:59 -0500
Message-ID: <1178120459.2953.16.camel@state.g2switchworks.com> (raw)
In-Reply-To: <910CF843580B3C40A25CD0D04B3908E213050E@exchange4.comune.prato.local>
References: <910CF843580B3C40A25CD0D04B3908E213050E@exchange4.comune.prato.local>
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.
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: smarlowe@g2switchworks.com, g.bartolini@comune.prato.it
Subject: Re: VACUUM FULL ANALYSE hanging
In-Reply-To: <1178120459.2953.16.camel@state.g2switchworks.com>
* 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