From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Sanyo Moura <sanyo(dot)moura(at)tatic(dot)net> |
Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 |
Date: | 2018-11-27 15:00:08 |
Message-ID: | 793.1543330808@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Sanyo Moura <sanyo(dot)moura(at)tatic(dot)net> writes:
> And below are the times generated by EXPLAIN ANALYZE:
> 10.5
> Planning time: 126.080 ms
> Execution time: 2.306 ms
> 11.0
> Planning Time: 7.238 ms
> Planning Time: 2.638 ms
> 11.5 (I assume you mean 11.1 here)
> Planning Time: 15138.533 ms
> Execution Time: 2.310 ms
There were no changes between 11.0 and 11.1 that look like they'd affect
planning time. Nor does it seem particularly credible that planning time
would have dropped by a factor of 15 between 10.x and 11.x, especially
not given that the resulting plan didn't change. I think you've got some
external factor causing long planning times --- maybe something taking an
exclusive lock on one of the tables, or on pg_statistic?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2018-11-27 15:02:38 | Re: Remove Deprecated Exclusive Backup Mode |
Previous Message | Peter Eisentraut | 2018-11-27 14:54:39 | Re: Remove Deprecated Exclusive Backup Mode |
From | Date | Subject | |
---|---|---|---|
Next Message | Sanyo Moura | 2018-11-27 15:11:49 | Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 |
Previous Message | Sanyo Moura | 2018-11-27 14:16:41 | Query with high planning time at version 11.1 compared versions 10.5 and 11.0 |