| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Forcing analyze on DB after upgrading? |
| Date: | 2019-10-30 05:48:43 |
| Message-ID: | 6912b4dadb63b3b766d3536b6d27d76840759f35.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, 2019-10-29 at 22:41 -0700, Wells Oliver wrote:
> Thanks! Unfortunately I can't find the shell script it created in /var/log/postgresql -- however,
> I ran vacuumdb --full --verbose --analyze-in-stages and the DB performs much, much better.
Ouch. --full might hurt.
> As I can't seem to find the script, anything else a good thing to do after doing pg_upgrade to prime the DB?
pg_upgrade recommends
vacuumdb --all --analyze-in-stages
which runs three analyze passes with different "default_statistics_target"
to get up and running as fast as possible, but if you can wait a little,
vacuumdb --all --analyze-only
will be faster.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pepe TD Vo | 2019-10-30 13:45:06 | commit & rollback |
| Previous Message | Wells Oliver | 2019-10-30 05:41:34 | Re: Forcing analyze on DB after upgrading? |