Re: Reducing memory consumed by RestrictInfo list translations in partitionwise join planning

amit <amitlangote09@gmail.com>

From: Amit Langote <amitlangote09@gmail.com>

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

Cc: David Rowley <dgrowleyml@gmail.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Dmitry Dolgov <9erthalion6@gmail.com>, tomas@vondra.me, vignesh C <vignesh21@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, Richard Guo <guofenglinux@gmail.com>

Date: 2025-04-04T08:52:08Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add assertion to verify derived clause has constant RHS
- 887160d1beae 18.0 landed
Make derived clause lookup in EquivalenceClass more efficient
- 88f55bc97622 18.0 landed
Doc: improve documentation for jsonpath behavior.
- 7014c9a4bba2 17.0 cited
Work around implementation restriction in adjust_appendrel_attrs.
- 767c598954bb 16.0 cited

On Fri, Apr 4, 2025 at 5:48 PM Ashutosh Bapat
<ashutosh.bapat.oss@gmail.com> wrote:
> On Fri, Apr 4, 2025 at 2:04 PM Amit Langote <amitlangote09@gmail.com> wrote:
> > I’ve now marked this as committed after pushing the patches earlier today.
>
> Thanks a lot.

Thank you too for working on it.

> > I realize the CF entry was originally about the project to reduce
> > memory usage during partitionwise join planning, but we ended up
> > committing something else. I suppose we can create a new entry if and
> > when we pick that original work back up.
>
> Will create a new CF entry just to keep the patch floated.

Sounds good.

Saving memory where we can does seem worthwhile, as long as the
approach stays simple. If there’s any doubt on that front, maybe it’s
worth spending a bit more time to see if things can be simplified.

-- 
Thanks, Amit Langote