| From: | Igor Neyman <ineyman(at)perceptron(dot)com> |
|---|---|
| To: | Krzysztof Plocharz <plocharz(at)9livesdata(dot)com>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: Planning performance problem (67626.278ms) |
| Date: | 2019-04-08 14:18:11 |
| Message-ID: | BN6PR1701MB1890448F8E5648C2495FC9D8DA2C0@BN6PR1701MB1890.namprd17.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
-----Original Message-----
From: Krzysztof Plocharz [mailto:plocharz(at)9livesdata(dot)com]
Sent: Monday, April 08, 2019 10:11 AM
To: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Planning performance problem (67626.278ms)
Hi
We have some very strange query planning problem. Long story short it takes 67626.278ms just to plan. Query execution takes 12ms.
Query has 7 joins and 2 subselects.
It looks like the issue is not deterministic, sometimes is takes few ms to plan the query.
One of the tables has 550,485,942 live tuples and 743,504,012 dead tuples. Running ANALYZE on that tables solves the problem only temporarily.
Question is how can we debug what is going on?
Best Regards,
Krzysztof Płocharz
_______________________________________________________________________________________________
Why do you have to run Analyze? Did you turn off Autovacuum?
Regards,
Igor Neyman
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Krzysztof Plocharz | 2019-04-08 14:28:02 | Re: Planning performance problem (67626.278ms) |
| Previous Message | Krzysztof Plocharz | 2019-04-08 14:10:52 | Planning performance problem (67626.278ms) |