Horton

Re: Problem with default partition pruning

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Amit Langote <amitlangote09@gmail.com>
Cc: yuzuko <yuzukohosoya@gmail.com>, shawn wang <shawn.wang.pg@gmail.com>, Shawn Wang <shawn.wang@highgo.ca>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-07-31T12:48:58Z
Lists: pgsql-hackers 
On 2019-Jul-31, Amit Langote wrote:

> Hello,
> 
> I noticed that the patch is still marked as "Waiting on Author" ever
> since Shawn set it that way on June 17.  Since Hosoya-san posted
> updated patches on June 27, the status should've been changed to
> "Needs Review".  Or maybe "Ready for Committer", because the last time
> I looked, at least the default partition pruning issue seems to be
> sufficiently taken care of by the latest patch.  Whether or not we
> should apply the other patch (more aggressive use of constraint
> exclusion by partprune.c on partitioned partitions), I'm not sure, but
> maybe a committer can decide in an instant. :)

Thanks for the status update.  I intend to get this patch pushed before
the next set of minors.

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

Commits

  1. Don't constraint-exclude partitioned tables as much

  2. Apply constraint exclusion more generally in partitioning

  3. Improve pruning of a default partition

  4. Doc: Fix event trigger firing table

  5. Remove obsolete nbtree insertion comment.