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: Justin Pryzby <pryzby@telsasoft.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2018-05-07T05:05:05Z
Lists: pgsql-hackers
Thanks for looking at this. I've taken most of your suggestions, some I had changed around as a result of Amit's review. On 7 May 2018 at 15:34, Justin Pryzby <pryzby@telsasoft.com> wrote: > + During actual execution of the query plan. Partition pruning may also > Remove "actual" ? I left this out one. I imagined it would be common to think of executor startup/execution/execution shutdown as "query execution", but I really only mean during the middle of those three things. If you can think of a better way to make that more clear, then it might be worth considering. For now, I think removing "actual" won't help. A patch will follow shortly, in response to Amit's review. -- 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