varo Herrera) Allow tables with
> thousands of child partitions to be processed efficiently by operations
> that only affect a small number of partitions." *
> https://www.postgresql.org/docs/12/release-12.html#id-1.11.6.5.5
> see more:
> https://www.postgresql.org/message-id/flat/9
your system:
> - PG version?
> - number of partitions?
> - any other important?
>
> for example - in PG 11.2 Changes:
> "Improve planning speed for large inheritance or partitioning table groups
> (Amit Langote, Etsuro Fujita)"
> https://www.postgresql.org/docs/current/rele
We encounter a issue when we do query on partition table directly with
proper partition key provide. postgres able to find problem partition but
when I do explain plan it showing 95% spend on planning the execution .
Here is example
itinerary=# EXPLAIN ANALYZE SELECT * FROM itinerary WHERE destinat
