Request a Demo
Home   >   mailing lists

Re: When deleting the plpgsql function, release the CachedPlan of the function - Mailing list pgsql-hackers

From Matthias van de Meent
Subject Re: When deleting the plpgsql function, release the CachedPlan of the function
Date
Msg-id CAEze2WgOLDRZr5Bu45iZCmdRPuC0TwFz5+yJRuD6zkz_ak8mRg@mail.gmail.com
Whole thread Raw
In response to When deleting the plpgsql function, release the CachedPlan of the function  ("zengman" <zengman@halodbtech.com>)
Responses Re: When deleting the plpgsql function, release the CachedPlan of the function
List pgsql-hackers
Tree view 
On Mon, 18 Aug 2025 at 08:51, zengman <zengman@halodbtech.com> wrote:
>
> Hi, hackers
>
> I have observed an issue where the CachedPlan corresponding to a function/procedure is not released when we execute
the"DROP FUNCTION\PROCEDURE" command. A patch to resolve this problem is attached.
 

I'm trying to figure out how this patch is supposed to handle
concurrent sessions dropping a procedure that has cached plans. AFAIK,
we don't execute RemoveFunctionById in other sessions, so this would
still leave the plan caches active for other backends, right?

Kind regards,

Matthias van de Meent
Databricks

pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: Proposal: Extending the PostgreSQL Protocol with Command Metadata
Next
From: Jacob Champion
Date:
Subject: Re: Proposal: Extending the PostgreSQL Protocol with Command Metadata