Horton

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

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Bruce Momjian <bruce@momjian.us>
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:23:17Z
Lists: pgsql-hackers 
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?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Tweak partitioning documentation wording

  2. docs: Rework sections on partition pruning/exclusion

  3. Add GUC enable_partition_pruning