David Wall wrote:
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 be
On Tue, Apr 27, 2010 at 2:50 PM, David Wall wrote:
> 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 t
On Tue, Apr 27, 2010 at 4:50 PM, David Wall 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, anyth
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 impressi
