| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Hasan Marzooq <engr(dot)naqvi(at)gmail(dot)com> |
| Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, "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 16:11:32 |
| Message-ID: | CAECtzeV1+iimVbSYkN32xQ5AFQOEZFj4phmMqFefuYsb4ZtDwA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le sam. 7 mai 2022 à 15:27, Hasan Marzooq <engr(dot)naqvi(at)gmail(dot)com> a écrit :
> Hello!
>
> Thanks Guillaume and Ron!
>
> I understand REINDEXING is not required, and as Guillaume highlighted,
> vacuum will still be needed after pg_restore.
>
> Is it ok to perform a "standard" vacuum or do we need a "FULL"
> vacuum after pg_restore?
>
>
You don't need VACUUM FULL.
> Also, I think finding tables which have dead rows and then performing
> vacuum on those tables only to save some time/processing here.
>
>
Finding dead rows in a table is interesting, but not right after a
pg_restore. pg_dump only dumps live tuples, so there won't be any dead rows
right after pg_restore.
--
Guillaume.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2022-05-08 07:09:27 | Re: Support logical replication of DDLs |
| Previous Message | David G. Johnston | 2022-05-07 14:41:44 | Re: PLPGSQL - extra column existence in trigger |