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

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>, Robert Haas <robertmhaas@gmail.com>, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, David Rowley <david.rowley@2ndquadrant.com>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2018-05-24T18:30:30Z
Lists: pgsql-hackers
On Thu, May 24, 2018 at 02:23:17PM -0400, Alvaro Herrera wrote:
> On 2018-May-24, Bruce Momjian wrote:
> 
> > On Wed, May  2, 2018 at 07:49:42PM -0700, David G. Johnston wrote:
> 
> > > I toss my +1 to removing it altogether.
> > 
> > +1  We are terrible at removing old GUCs and having it around means
> > everyone has to decide if they need to change it, so having it is not a
> > zero cost.
> 
> Are you voting to remove the GUC?

Yes.  Sorry but I am very late on this and maybe too late to vote.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +


Commits

  1. Tweak partitioning documentation wording

  2. docs: Rework sections on partition pruning/exclusion

  3. Add GUC enable_partition_pruning