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

Alvaro Herrera <alvherre@2ndquadrant.com>

From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: David Rowley <david.rowley@2ndquadrant.com>, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2018-05-10T16:58:49Z
Lists: pgsql-hackers
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.

-- 
Á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