Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0

Amit Langote <langote_amit_f8@lab.ntt.co.jp>

From: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
To: Alvaro Herrera <alvherre@2ndquadrant.com>, Justin Pryzby <pryzby@telsasoft.com>
Cc: Sanyo Moura <sanyo.moura@tatic.net>, jeff.janes@gmail.com, David Rowley <david.rowley@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, pgsql-performance@lists.postgresql.org, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2018-12-06T02:19:24Z
Lists: pgsql-hackers, pgsql-performance
On 2018/12/06 11:14, Amit Langote wrote:
> I ran the original unmodified query at [1] (the one that produces an empty
> plan due to all children being pruned) against the server built with
> patches I posted on the "speeding up planning with partitions" [2] thread
> and it finished in a jiffy.

Forgot to add the link for [2]: https://commitfest.postgresql.org/21/1778/

Thanks,
Amit



Commits

  1. Postpone generating tlists and EC members for inheritance dummy children.

  2. Allow direct lookups of AppendRelInfo by child relid