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: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>,
Alvaro Herrera <alvherre@alvh.no-ip.org>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2018-05-02T23:52:27Z
Lists: pgsql-hackers
On 3 May 2018 at 11:38, David G. Johnston <david.g.johnston@gmail.com> wrote: > Maybe "Partition Filtering" (I'm disliking selection, I'm thinking we must > always select partitions) I don't see why "Filtering" is any different from pruning, they both imply removing something that was once there. What I'm saying is, that it's backward to think of what we have now as pruning, so I don't think renaming it to "partition filtering" addresses my concern. FWIW, I'm not set on changing this. I just want to discuss this now so that the chances of having regrets about this later are reduced. -- 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