Horton

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

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: David Rowley <david.rowley@2ndquadrant.com>, Justin Pryzby <pryzby@telsasoft.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-10T20:05:04Z
Lists: pgsql-hackers 
On Thu, May 10, 2018 at 3:45 PM, Alvaro Herrera
<alvherre@2ndquadrant.com> wrote:
> The examples for runtime pruning are lame -- in the first, the text says
> "watch out for Subplans Removed" and then the example provided doesn't
> show one.  (That example is probably exercising the wrong thing.)

It seems to me that EXPLAIN output should have a clear way to show --
and to distinguish -- (1) plan-time pruning, (2) executor startup time
pruning, (3) mid-execution pruning.  I don't think that's entirely the
case right now.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

  1. Tweak partitioning documentation wording

  2. docs: Rework sections on partition pruning/exclusion

  3. Add GUC enable_partition_pruning