Horton

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

Justin Pryzby <pryzby@telsasoft.com>

View thread View on postgr.es
From: Justin Pryzby <pryzby@telsasoft.com>
To: David Rowley <david.rowley@2ndquadrant.com>
Cc: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2018-05-08T13:32:05Z
Lists: pgsql-hackers 
On Mon, May 07, 2018 at 06:00:59PM +1200, David Rowley wrote:
> Many thanks for reviewing this.

2nd round - from the minimalist department:

+    partitions which cannot possibly contain any matching records.
maybe: partitions which cannot match any records.

+   <para>
+    Partition pruning done during execution can be performed at any of the
+    following times:

remove "done"?

+       number of partitions which were removed during this phase of pruning by
remove "of prunning"

Justin

Commits

  1. Tweak partitioning documentation wording

  2. docs: Rework sections on partition pruning/exclusion

  3. Add GUC enable_partition_pruning