From: | Harold Falkmeyer <hfalkmeyer(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Restoring From Backups |
Date: | 2017-06-07 19:09:26 |
Message-ID: | CACcYriu4d8am_8nso7m94V4=8MG+_cmk1Lo=t0NHJ4m6odEknA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Greetings,
Three'ish more questions:
When restoring a table from backup (using pg_dump and pg_restore), are
there reasons, other than restoration performance, to defer index
restoration until after the COPY is complete?
After completing a COPY into a fresh table, is there any benefit to running
a subsequent VACUUM (given that there shouldn't be any dead tuples)?
As we understand it, an ANALYZE is necessary, regardless if we restore to a
table with preexisting indexes or one that's had indexes added after the
fact. Is this correct? Put slightly a different way, do CREATE INDEX
and/or REINDEX operations cause stats updates?
Thank you in advance,
Harold Falkmeyer
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-06-07 19:28:55 | Re: Restoring From Backups |
Previous Message | David G. Johnston | 2017-06-07 14:40:18 | Re: How to build a distributed pg-10.0 cluster |