Re: generic plans and "initial" pruning - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: generic plans and "initial" pruning
Date
Msg-id 668eb809-cf43-4d93-b1a7-04d9f865960b@vondra.me
Whole thread Raw
In response to Re: generic plans and "initial" pruning  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: generic plans and "initial" pruning
List pgsql-hackers
On 5/20/25 05:06, Tom Lane wrote:
> Amit Langote <amitlangote09@gmail.com> writes:
>> Pushed after some tweaks to comments and the test case.
> 
> My attention was drawn to commit 525392d57 after observing that
> Valgrind complained about a memory leak in some code that commit added
> to BuildCachedPlan().  I tried to make sense of said code so I could
> remove the leak, and eventually arrived at the attached patch, which
> is part of a series of leak-fixing things hence the high sequence
> number.
> 
> Unfortunately, the bad things I speculated about in the added comments
> seem to be reality.  The second attached file is a test case that
> triggers
> 
> ...

FYI I added this as a PG18 open item:

  https://wiki.postgresql.org/wiki/PostgreSQL_18_Open_Items


regards

-- 
Tomas Vondra




pgsql-hackers by date:

Previous
From: Anthonin Bonnefoy
Date:
Subject: Re: Regression in statement locations
Next
From: jian he
Date:
Subject: cookConstraint dead code