| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Ron <ronljohnsonjr(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 10:06:42 |
| Message-ID: | CAECtzeXtrwxGgiWNb_qsTG-tm8fyTsgLdfguWNhjni+1_H8qDg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le sam. 7 mai 2022 à 10:21, Ron <ronljohnsonjr(at)gmail(dot)com> a écrit :
> On 5/6/22 21:35, Hasan Marzooq wrote:
>
> 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.
>
>
> Perform VACUUM after there have been many updates and deletes. There have
> been zero updates and deleted after pg_restore; therefore, *no need to
> vacuum*.
>
>
I disagree. You're right about the "zero updates and deletes", so no need
to vacuum for bloat. But you need vacuum to get the visibility map of each
relation, so that the planner can use index-only scans.
--
Guillaume.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Durumdara | 2022-05-07 13:02:09 | PLPGSQL - extra column existence in trigger |
| Previous Message | Ron | 2022-05-07 08:21:30 | Re: pg_dump: VACUUM and REINDEXING |