On Wed, Sep 13, 2017 at 4:07 PM, Ashutosh Bapat <ashutosh.ba...@enterprisedb.com> wrote: > For a partitioned table, this patch saves the time to run constraint > exclusion on all the partitions if constraint exclusion succeeds on > the partitioned table. If constraint exclusion fails, we have wasted > CPU cycles on one run of constraint exclusion. The difference between > the time spent in the two scenarios increases with the number of > partitions. Practically, users will have a handful partitions rather > than a couple and thus running overhead of running constraint > exclusion on partitioned table would be justified given the time it > will save when CE succeeds.
Moved patch to next CF. -- Michael
