Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id DD2079FBC25 for ; Wed, 2 May 2007 12:41:03 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 52760-08 for ; Wed, 2 May 2007 12:41:00 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id 741279FBBDB for ; Wed, 2 May 2007 12:41:00 -0300 (ADT) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Wed, 2 May 2007 15:40:59 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 02 May 2007 10:40:59 -0500 Subject: Re: VACUUM FULL ANALYSE hanging From: Scott Marlowe To: Gabriele Bartolini Cc: pgsql-admin@postgresql.org In-Reply-To: <910CF843580B3C40A25CD0D04B3908E213050E@exchange4.comune.prato.local> References: <910CF843580B3C40A25CD0D04B3908E213050E@exchange4.comune.prato.local> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1178120459.2953.16.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Wed, 02 May 2007 10:40:59 -0500 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/22 X-Sequence-Number: 25342 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.