Re: Problem with default partition pruning

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: shawn wang <shawn(dot)wang(dot)pg(at)gmail(dot)com>
Cc: Shawn Wang <shawn(dot)wang(at)highgo(dot)ca>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Yuzuko Hosoya <yuzukohosoya(at)gmail(dot)com>
Subject: Re: Problem with default partition pruning
Date: 2019-06-24 03:45:37
Message-ID: 20190624034537.GA21833@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-Jun-24, shawn wang wrote:

Hello,

> Thank you for your reply.
> You can see that the mail start time is February 22. So I looked at the
> latest version at that time. I found that v11.2 was the newest branch at
> the time. So I tried to merge this patch into the code, and I found that
> everything worked.

I see -- I only tried master, didn't occur to me to try it against
REL_11_STABLE.

> So I tested on this branch and got the results.
> You need to add the v4_default_partition_pruning.patch
> <https://www.postgresql.org/message-id/attachment/100463/v4_default_partition_pruning.patch>
> first,
> and then add the
> v3_ignore_contradictory_where_clauses_at_partprune_step.patch
> <https://www.postgresql.org/message-id/attachment/100591/v3_ignore_contradictory_where_clauses_at_partprune_step.patch>

Oh, so there are two patches? It's easier to keep track if they're
always posted together. Anyway, I may have some time to have a look
tomorrow (Monday).

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-06-24 04:06:16 Re: check_recovery_target_lsn() does a PG_CATCH without a throw
Previous Message Binguo Bao 2019-06-24 02:53:49 Re: Optimize partial TOAST decompression