| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Hasan Marzooq <engr(dot)naqvi(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_dump: VACUUM and REINDEXING |
| Date: | 2022-05-07 07:36:17 |
| Message-ID: | CAECtzeUA=xLYPw55VpZyKj=Dxv32kzhb8MHAvB2CvC5xObOUBg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
Le sam. 7 mai 2022 à 04:36, Hasan Marzooq <engr(dot)naqvi(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2022-05-07 08:21:30 | Re: pg_dump: VACUUM and REINDEXING |
| Previous Message | David G. Johnston | 2022-05-07 04:46:34 | Re: "A transaction cannot be ended inside a block with exception handlers." |