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

From zengman
Subject Re: Re: When deleting the plpgsql function, release the CachedPlan of the function
Date
Msg-id tencent_4335FC35086A1BE6369D2B86@qq.com
Whole thread Raw
In response to When deleting the plpgsql function, release the CachedPlan of the function  ("zengman" <zengman@halodbtech.com>)
List pgsql-hackers
That's correct—this is a simple and blunt patch, and it fails to account for many factors. Initially, I wasn't even sure if this qualified as a distinct issue. Your solution is far more reasonable, and I will rethink the new implementation thoroughly based on your approach.

Thanks,
Zeng Man

Tom Lane<tgl@sss.pgh.pa.us> 在 2025年8月19日 周二 0:38 写道:
> It doesn't, which is (one reason) why it's just a crude hack.

> A more appropriate solution would be to make plpgsql install
> a shared-cache-invalidation callback that would watch for

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Logical Replication of sequences
Next
From: Naga Appani
Date:
Subject: Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring