On Fri, 30 Nov 2018 at 19:44, Amit Langote
<Langote_Amit_f8@lab.ntt.co.jp> wrote:
> Yeah, maybe we haven't explained in the documentation where generic plans
> are described that making them for partitioned table is an expensive
> affair. Although, by definition, they are built once for a given query
> and PG 11 with it's execution-time pruning can execute these plans pretty
> quickly, which is an overall improvement. But you'd obviously know that
> much. :)
Maybe a documents patch is a good idea. Your planner patches for
partitioning are only going to widen the performance gap between
generating a plan where many partitions are pruned vs generating a
generic plan where no partition could be pruned. I can only imagine
this will cause problems for more people as that gap widens as it will
likely lead to more and more people with partitioned tables with high
numbers of partitions.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
