Re: Should we add GUCs to allow partition pruning to be disabled? - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Should we add GUCs to allow partition pruning to be disabled?
Date
Msg-id CAKFQuwYrZL5K7pFx0Vrk7bfVvyqbAWNpyaVZJ2xSR5dvQ=isJw@mail.gmail.com
Whole thread Raw
In response to Re: Should we add GUCs to allow partition pruning to be disabled?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Should we add GUCs to allow partition pruning to be disabled?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Thu, May 10, 2018 at 10:13 AM, Robert Haas <robertmhaas@gmail.com> wrote:
On Thu, May 10, 2018 at 12:58 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> David G. Johnston wrote:
>> As a user I don't really need to know which model is implemented and the
>> name doesn't necessarily imply the implementation.  Pruning seems to be the
>> commonly-used term for this feature and we should stick with that.
>
> I agree with this conclusion.  So we have it right and we shouldn't
> change it.

+1.


​Seems like if it stays the name is good - but at this point no has voiced opposition to removing it and making the name a moot point.

David J.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ts_rewrite in 10.4
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] Cutting initdb's runtime (Perl question embedded)