| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Krzysztof Plocharz <plocharz(at)9livesdata(dot)com> |
| Cc: | "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:33:34 |
| Message-ID: | CAFj8pRDDnOVNcU7dx4+oKH0x4-DsmL3XRWppQ8Cf5wwJ=G2fPg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
po 8. 4. 2019 v 16:11 odesílatel Krzysztof Plocharz <plocharz(at)9livesdata(dot)com>
napsal:
> 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?
>
please check your indexes against bloating. Planner get min and max from
indexes and this operation is slow on bloat indexes.
but 67 sec is really slow - it can be some other other problem - it is real
computer or virtual?
>
> Best Regards,
> Krzysztof Płocharz
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2019-04-08 14:42:10 | Re: Planning performance problem (67626.278ms) |
| Previous Message | Krzysztof Plocharz | 2019-04-08 14:28:02 | Re: Planning performance problem (67626.278ms) |