I currently have version 11.1 and 10.6 running on the same linux server. In both Postgres the "Price" table has 730 partitions.
However, in the test I did in version 11.0, "Precio" is partitioned into only 21 partitions. So it really is a problem introduced in version 11, and it has to do with a large number of partitions in a table.
Sanyo
Em ter, 27 de nov de 2018 às 23:27, Justin Pryzby <pryzby@telsasoft.com> escreveu:
On Tue, Nov 27, 2018 at 06:44:02PM -0600, Justin Pryzby wrote: > On Tue, Nov 27, 2018 at 9:17 AM Sanyo Moura <sanyo.moura@tatic.net> wrote: > >>> I'm running performance tests for my application at version 11.1 and > >>> encountered queries with high planning time compared to the same planning, > >>> running at versions 10.5 and 11.0. > > I was able to reproduce this behavior.
I take that back, in part..
My query (with One-Time Filter: false) has high planning time under 11.0, also:
| Result (cost=0.00..0.00 rows=0 width=24) | One-Time Filter: false |Time: 48335.098 ms (00:48.335)
