From: | Krzysztof Plocharz <plocharz(at)9livesdata(dot)com> |
---|---|
To: | pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Re: Planning performance problem (67626.278ms) |
Date: | 2019-04-08 14:28:02 |
Message-ID: | aac8b78f-5f28-7b7d-1ee7-7f5d247466d9@9livesdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
No, Autovacuum is running.
On 2019/04/08 16:18, Igor Neyman wrote:
>
> -----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 | Pavel Stehule | 2019-04-08 14:33:34 | Re: Planning performance problem (67626.278ms) |
Previous Message | Igor Neyman | 2019-04-08 14:18:11 | RE: Planning performance problem (67626.278ms) |