Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id D2FCB9FBAED for ; Tue, 15 May 2007 19:45:22 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 27845-06 for ; Tue, 15 May 2007 19:45:07 -0300 (ADT) X-Greylist: delayed 00:31:05.202504 by SQLgrey-1.7.5 Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 064A09FBB7C for ; Tue, 15 May 2007 19:45:10 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from mail27.syd.optusnet.com.au (mail27.syd.optusnet.com.au [211.29.133.168]) by svr4.postgresql.org (Postfix) with ESMTP id 8AB815AF02A for ; Tue, 15 May 2007 22:14:04 +0000 (GMT) Received: from www3.nicku.org (c211-30-174-44.farfl1.nsw.optusnet.com.au [211.30.174.44]) by mail27.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id l4FMDwn9027513; Wed, 16 May 2007 08:13:58 +1000 Received: from localhost (localhost.localdomain [127.0.0.1]) by www3.nicku.org (Postfix) with ESMTP id 3330B246DE6; Wed, 16 May 2007 08:13:58 +1000 (EST) X-Virus-Scanned: amavisd-new at example.com Received: from www3.nicku.org ([127.0.0.1]) by localhost (www3.nicku.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HKsQAJ8tWKTN; Wed, 16 May 2007 08:13:56 +1000 (EST) Received: by www3.nicku.org (Postfix, from userid 1000) id DD07E246F5B; Wed, 16 May 2007 08:13:56 +1000 (EST) Date: Wed, 16 May 2007 08:13:56 +1000 From: Nick Urbanik To: pgsql-admin@postgresql.org Subject: How overcome wait for vacuum full? Message-ID: <20070515221356.GG5264@nicku.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oOB74oR0WcNeq9Zb" Content-Disposition: inline User-Agent: Mutt/1.4.2.2i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/119 X-Sequence-Number: 25439 --oOB74oR0WcNeq9Zb Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Dear Folks, I am running a full vacuum on a database. It's taking longer than I hoped. In particular, the vacuum still hasn't reached the table that will benefit most from the vacuum. Can I move the existing table to a backup, make a copy of the table back to its original name, restart the application, and run the vacuum on the backup? Or can I reclaim the disk space by dropping the original after making a copy? If I can, without losing data, what is the best way to do that? I am reaching the end of the period when this database application can be disabled. I have never run vacuum full on such a large database (24G) and am desperate to get the application back online. --=20 Nick Urbanik RHCE http://nicku.org nicku@nicku.org GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24 --oOB74oR0WcNeq9Zb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFGSjCkFt/sW7udLCQRAoEoAJ9K4Ul4N6O/1luBAJ0l3u6JHqvuVgCgpNyx tMElkB3gfzeb+VH0isGgUK4= =RwTZ -----END PGP SIGNATURE----- --oOB74oR0WcNeq9Zb--