| From: | johannes graën <johannes(at)selfnet(dot)de> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: performance drop after upgrade (9.6 > 10) |
| Date: | 2017-10-24 14:15:59 |
| Message-ID: | CA++JNSfTEifSiBq73zpGCQuDNGr9yYcjmkx_=LtAbnadKLY_vg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Hi Pavel, *,
you were right with ANALYZing the DB first. However, even after doing
so, I frequently see Seq Scans where an index was used before. This
usually cooccurs with parallelization and looked different before
upgrading to 10. I can provide an example for 10 [1], but I cannot
generate a query plan for 9.6 anymore.
Any ideas what makes the new version more seqscanny?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-10-24 14:17:21 | Re: Current int & float overflow checking is slow. |
| Previous Message | Gaddam Sai Ram | 2017-10-24 14:12:13 | CurTransactionContext freed before transaction COMMIT ??? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | legrand legrand | 2017-10-24 14:51:11 | Re: postgresql tuning with perf |
| Previous Message | Purav Chovatia | 2017-10-24 11:39:01 | Re: postgresql tuning with perf |