From: Nick Urbanik <nicku@nicku.org>
To: pgsql-admin@postgresql.org
Subject: How overcome wait for vacuum full?
Date: Wed, 16 May 2007 08:13:56 +1000
Message-ID: <20070515221356.GG5264@nicku.org> (raw)
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.
--
Nick Urbanik RHCE http://nicku.org nicku@nicku.org
GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24
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: nicku@nicku.org
Subject: Re: How overcome wait for vacuum full?
In-Reply-To: <20070515221356.GG5264@nicku.org>
* 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