Re: A problem about partitionwise join

From: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
To: Richard Guo <riguo(at)pivotal(dot)io>
Cc: Amit Langote <amitlangote09(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: A problem about partitionwise join
Date: 2019-08-30 06:13:37
Message-ID: CAPmGK1464r7bWQJVTYkJj7U=eAJXyjAtLDmfWjau65Gubf+MxQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 30, 2019 at 12:15 PM Richard Guo <riguo(at)pivotal(dot)io> wrote:
> On Fri, Aug 30, 2019 at 2:08 AM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> wrote:
>> On Thu, Aug 29, 2019 at 6:45 PM Richard Guo <riguo(at)pivotal(dot)io> wrote:
>> > Attached is a patch as an attempt to address this issue. The idea is
>> > quite straightforward. When building partition info for joinrel, we
>> > generate any possible EC-derived joinclauses of form 'outer_em =
>> > inner_em', which will be used together with the original restrictlist to
>> > check if there exists an equi-join condition for each pair of partition
>> > keys.

>> Could you add the patch to the
>> upcoming CF so that it doesn’t get lost?

> Added this patch: https://commitfest.postgresql.org/24/2266/

Thanks!

Best regards,
Etsuro Fujita

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2019-08-30 06:28:12 Re: Memory-Bounded Hash Aggregation
Previous Message Peter Geoghegan 2019-08-30 05:10:14 Re: [HACKERS] [WIP] Effective storage of duplicates in B-tree index.