Re: VACUUM FULL vs backup/restore

From: Vick Khera <vivek(at)khera(dot)org>
To: Postgres General Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: VACUUM FULL vs backup/restore
Date: 2010-04-27 21:50:45
Message-ID: g2v2968dfd61004271450m1d84fe5bq7b48333821b330a3@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Apr 27, 2010 at 4:50 PM, David Wall <d(dot)wall(at)computer(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2010-04-27 22:00:51 Re: VACUUM FULL vs backup/restore
Previous Message Chris Copeland 2010-04-27 21:32:30 Re: Server Panic when trying to stop point in time recovery