Horton

Re: Problem with default partition pruning

yuzuko <yuzukohosoya@gmail.com>

View thread View on postgr.es
From: yuzuko <yuzukohosoya@gmail.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>, shawn wang <shawn.wang.pg@gmail.com>
Cc: Shawn Wang <shawn.wang@highgo.ca>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-06-27T02:34:13Z
Lists: pgsql-hackers

Attachments

Hello,

On Tue, Jun 25, 2019 at 1:45 PM yuzuko <yuzukohosoya@gmail.com> wrote:
>
> Hello Shawn, Alvaro,
>
> Thank you for testing patches and comments.
> Yes, there are two patches:
> (1) v4_default_partition_pruning.patch fixes problems with default
> partition pruning
> and (2) v3_ignore_contradictory_where_clauses_at_partprune_step.patch determines
> if a given clause contradicts a sub-partitioned table's partition constraint.
> I'll post two patches together next time.
>
> Anyway, I'll rebase two patches to apply on master and fix space.
>

Attach the latest patches discussed in this thread.  I rebased the second
patch (v5_ignore_contradictory_where_clauses_at_partprune_step.patch)
on the current master.  Could you please check them again?

--
Best regards,
Yuzuko Hosoya
NTT Open Source Software Center

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.