Postgres Pro
Downloads
Home   >   mailing lists

Re: VACUUM FULL vs backup/restore - Mailing list pgsql-general

From Vick Khera
Subject Re: VACUUM FULL vs backup/restore
Date
Msg-id g2v2968dfd61004271450m1d84fe5bq7b48333821b330a3@mail.gmail.com
Whole thread Raw
In response to VACUUM FULL vs backup/restore  (David Wall <d.wall@computer.org>)
List pgsql-general
Tree view 
On Tue, Apr 27, 2010 at 4:50 PM, David Wall <d.wall@computer.org> wrote:
> It seems my options are 1) VACUUM FULL with a reindex_db; or 2) backup, then
> restore.
>

I'd go with the backup+restore.  The other option is to to a trivial
ALTER to one of your fields which causes the table to be rewritten.

Basically, anything is faster than a VACUUM FULL in my experience.

pgsql-general by date:

Previous
From: Chris Copeland
Date:
Subject: Re: Server Panic when trying to stop point in time recovery
Next
From: Scott Marlowe
Date:
Subject: Re: VACUUM FULL vs backup/restore