| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Zahir Lalani <ZahirLalani(at)oliver(dot)agency> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PG10 upgrade issue |
| Date: | 2019-06-02 23:18:28 |
| Message-ID: | 26624.1559517508@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Zahir Lalani <ZahirLalani(at)oliver(dot)agency> writes:
> We have done pg10 upgrades from 9.6 on all our environments successfully. We have an automation script that does this for us. One environment is a near replica of our production setup and all works fine.
> We have now made 2 attempts at doing this on production - both ending up with rollback
> The key issue we have is that all queries were incredibly slow. The PG 10 postmaster workers would all show 100% cpu, especially on the replicas. We even increased CPUs but that made no difference.
Did you make sure to rebuild statistics (re-ANALYZE) after the upgrade?
pg_upgrade makes a script for that, but I don't believe it runs it for
you.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zahir Lalani | 2019-06-02 23:52:15 | Re: PG10 upgrade issue |
| Previous Message | Zahir Lalani | 2019-06-02 23:10:05 | PG10 upgrade issue |