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: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Cc: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2018-04-20T02:41:13Z
Lists: pgsql-hackers
On 20 April 2018 at 14:33, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> wrote: > On 2018/04/20 11:18, David Rowley wrote: >> 4. Replace test doing (constraint_exclusion == >> CONSTRAINT_EXCLUSION_PARTITION) with (enable_partition_pruning). >> 5. Get rid of CONSTRAINT_EXCLUSION_PARTITION. > > About 4 & 5: > > Perhaps we should leave constraint_exclusion = partition alone because > there might be users who want to continue using the old inheritance method > to set up partitioning for whatever reason? Yeah, for some reason that keeps falling out my brain. -- 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