Re: Should we add GUCs to allow partition pruning to be disabled?

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Should we add GUCs to allow partition pruning to be disabled?
Date: 2018-05-10 17:38:41
Message-ID: CAKFQuwYrZL5K7pFx0Vrk7bfVvyqbAWNpyaVZJ2xSR5dvQ=isJw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 10, 2018 at 10:13 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> On Thu, May 10, 2018 at 12:58 PM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2018-05-10 17:40:58 Re: [HACKERS] Cutting initdb's runtime (Perl question embedded)
Previous Message Tom Lane 2018-05-10 17:16:17 Re: ts_rewrite in 10.4