On Mon, 18 Aug 2025 at 08:51, zengman <[email protected]> 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
