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

From David Wall
Subject VACUUM FULL vs backup/restore
Date
Msg-id 4BD74E22.3050003@computer.org
Whole thread Raw
Responses Re: VACUUM FULL vs backup/restore  (Vick Khera <vivek@khera.org>)
Re: VACUUM FULL vs backup/restore  (Scott Marlowe <scott.marlowe@gmail.com>)
Re: VACUUM FULL vs backup/restore  (Greg Smith <greg@2ndquadrant.com>)
List pgsql-general
We are copying a production database and then pairing it down
dramatically (perhaps removing 99% of records, most of which are large
objects).

It seems my options are 1) VACUUM FULL with a reindex_db; or 2) backup,
then restore.

Is there anything one does better than the other?  Our impression is
that the backup and restore will run faster (perhaps 2 hours), whereas
we have a currently running VACUUM FULL that's been running for 4.5
hours already.

Anybody have any experience on this?  Would a backup/restore essentially
create a minimally sized database with all fresh indexes?

Thanks,
David

pgsql-general by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Open Source BI Tool
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Server Panic when trying to stop point in time recovery