Re: [PoC] Reducing planning time when tables have many partitions - Mailing list pgsql-hackers

From Yuya Watari
Subject Re: [PoC] Reducing planning time when tables have many partitions
Date
Msg-id CAJ2pMkYaDgnwL0nF=DGq5eky1RBxj4tfqHwFSmTJC1XUmX6_1w@mail.gmail.com
Whole thread Raw
In response to Re: [PoC] Reducing planning time when tables have many partitions  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
List pgsql-hackers
Hello Ashutosh,

Thank you for your detailed review, and apologies for my delayed response.

On Thu, Mar 27, 2025 at 1:42 PM Ashutosh Bapat
<ashutosh.bapat.oss@gmail.com> wrote:
>
> Here are memory consumption numbers using list_free() instead of pfree(), using the same method as [1], using a
binarywithout asserts and debug info. PFA the patchset where all the patches are the same as v35 but with an extra
patchfixing memory leak. The memory leak is visible with a higher number of joins. At a lower number of joins, I expect
thatthe memory saved is less than a KB or the leaked memory fits within 1 chunk of memory context and hence not
visible.

Thank you for conducting your benchmarks. Your results clearly show
increased memory consumption with my patches. As Tom also suggested,
we may reduce memory usage by adopting a different design. I will
reconsider alternative approaches and compare the memory usage to the
current version.

Thank you once again for conducting the benchmarks.

--
Best regards,
Yuya Watari



pgsql-hackers by date:

Previous
From: Yuya Watari
Date:
Subject: Re: [PoC] Reducing planning time when tables have many partitions
Next
From: Yugo Nagata
Date:
Subject: Improve coments on structures in trigger.c