Re: Memory consumed by child SpecialJoinInfo in partitionwise join planning - Mailing list pgsql-hackers

From Ashutosh Bapat
Subject Re: Memory consumed by child SpecialJoinInfo in partitionwise join planning
Date
Msg-id CAExHW5tJU=gg6L5t5yqfLBv-+bO3NcNZKziKfciSJPStjOmh7g@mail.gmail.com
Whole thread Raw
In response to Re: Memory consumed by child SpecialJoinInfo in partitionwise join planning  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers


On Mon, Mar 25, 2024 at 4:01 PM Amit Langote <amitlangote09@gmail.com> wrote:
On Mon, Mar 25, 2024 at 7:25 PM Richard Guo <guofenglinux@gmail.com> wrote:
> On Mon, Mar 25, 2024 at 5:17 PM Amit Langote <amitlangote09@gmail.com> wrote:
>> I've pushed this now.
>>
>> When updating the commit message, I realized that you had made the
>> right call to divide the the changes around not translating the dummy
>> SpecialJoinInfos into a separate patch.  So, I pushed it like that.
>
>
> Sorry I'm late for the party.  I noticed that in commit 6190d828cd the
> comment of init_dummy_sjinfo() mentions the non-existing 'rel1' and
> 'rel2', which should be addressed.

Thanks for catching that.  Oops.

Good catch.
 

>  Also, I think we can make function
> consider_new_or_clause() call init_dummy_sjinfo() to simplify the code a
> bit.

Indeed.

Thanks for fixing it.

--
Best Wishes,
Ashutosh Bapat

pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: DOCS: add helpful partitioning links
Next
From: Jelte Fennema-Nio
Date:
Subject: Re: session username in default psql prompt?