Re: Should we add GUCs to allow partition pruning to be disabled?
David Rowley <david.rowley@2ndquadrant.com>
From: David Rowley <david.rowley@2ndquadrant.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2018-04-26T02:54:42Z
Lists: pgsql-hackers
On 24 April 2018 at 09:10, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > I just pushed David patch, with some pretty minor changes. I hope not > to have broken anything. Thanks for pushing and thanks Amit for reviewing. The only thing that stands out in the actual commit is: + executor to remove (ignore) partitions during query execution. The I had originally written: + executor to remove or ignore partitions during query execution. The The reason I was using "remove or ignore" was that partitions pruned during init plan are effectively "removed" from the plan, whereas partitions pruned during the running of the planner are just "ignored". It's minor details but I thought I'd better point it out. -- David Rowley http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Commits
-
Tweak partitioning documentation wording
- 12b9affb32a6 11.0 landed
-
docs: Rework sections on partition pruning/exclusion
- bebc46931a12 11.0 landed
-
Add GUC enable_partition_pruning
- 055fb8d33da6 11.0 landed