From: Nick Urbanik <nicku@nicku.org>
To: pgsql-admin@postgresql.org
Subject: Re: How overcome wait for vacuum full?
Date: Wed, 16 May 2007 09:25:05 +1000
Message-ID: <20070515232505.GA16021@nicku.org> (raw)
In-Reply-To: <464A3E24.6060204@polimetrix.com>
References: <20070515221356.GG5264@nicku.org>
<464A3E24.6060204@polimetrix.com>
Thank you Geoff,
On 15/05/07 16:11 -0700, Geoff Tolley wrote:
>Nick Urbanik wrote:
>If you're waiting on vacuum to get around to the one table, you can run
>VACUUM FULL <tablename> instead.
Clearly that is what I should have done! It has reached the table now.
>
>Personally I've found that dropping indices (including the PK), then
>vacuum full, then recreating indices can be an awful lot faster than
>just leaving vacuum full to its own devices.
I'll investigate this for next time.
>Yes you ought to be able to reclaim disk space by the copy/drop
>original/rename procedure, but that gets hard to manage if you have
>triggers or foreign keys on the table in question. You might want to
>use CREATE TABLE table_copy (LIKE orig_table) to preserve column
>defaults if you go down that path.
It seems that PostgreSQL 7.3.8 does not support create table
table_name like original_table.
Can you suggest a way I can create a duplicate table with the same
triggers and other stuff that this table has?
What is the most efficient way to copy the data?
--
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: <20070515232505.GA16021@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