Re: pg_dump: VACUUM and REINDEXING - Mailing list pgsql-general

From Guillaume Lelarge
Subject Re: pg_dump: VACUUM and REINDEXING
Date
Msg-id CAECtzeUA=xLYPw55VpZyKj=Dxv32kzhb8MHAvB2CvC5xObOUBg@mail.gmail.com
Whole thread Raw
In response to pg_dump: VACUUM and REINDEXING  (Hasan Marzooq <engr.naqvi@gmail.com>)
List pgsql-general
Hi,

Le sam. 7 mai 2022 à 04:36, Hasan Marzooq <engr.naqvi@gmail.com> a écrit :
Hello!

I've some questions around Backup & Restore.

1: Is it necessary to perform a VACUUM and REINDEXING operation after restoring the dump from Postgres 9.6 to Postgres 13? The dump size could be 1/2 TB to 1 TB.


You can perform a VACUUM and an ANALYZE right after restoring, but you definitely shouldn't REINDEX.
 
2: Also, are there any other operations that are recommended to perform after pg_restore? 


I don't think you need anything else.
 
3: What is the minimum required disk space if taking a dump on the same machine where the source database exists? Is it the "size of the current data folder x 2"?


There's definitely no rules like that. It's impossible to know before doing it.


--
Guillaume.

pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: "A transaction cannot be ended inside a block with exception handlers."
Next
From: Ron
Date:
Subject: Re: pg_dump: VACUUM and REINDEXING