Horton

Re: Memory consumed by child SpecialJoinInfo in partitionwise join planning

Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>

View thread View on postgr.es
From: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
To: Amit Langote <amitlangote09@gmail.com>
Cc: Andrei Lepikhov <a.lepikhov@postgrespro.ru>, Richard Guo <guofenglinux@gmail.com>, Tomas Vondra <tomas.vondra@enterprisedb.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, vignesh C <vignesh21@gmail.com>
Date: 2024-03-25T10:10:00Z
Lists: pgsql-hackers 
On Mon, Mar 25, 2024 at 2:47 PM Amit Langote <amitlangote09@gmail.com>
wrote:

> > Attached patches
> > Squashed your 0001 and 0002 into 0001. I have also reworded the commit
> message to reflect the latest code changes.
> > 0002 has some minor edits. Please feel free to include or reject when
> committing the patch.
>
> I've pushed this now.
>

Thanks a lot.


>
> 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.
>
>
Ok. Thanks for separating the changes.

-- 
Best Wishes,
Ashutosh Bapat

Commits

  1. Code review for 6190d828cd2

  2. Do not translate dummy SpecialJoinInfos for child joins

  3. Reduce memory used by partitionwise joins

  4. Remove dummy_spinlock