Horton

Re: Re: When deleting the plpgsql function, release the CachedPlan of the function

zengman <zengman@halodbtech.com>

View thread
From: zengman <zengman@halodbtech.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, Matthias van de Meent <boekewurm+postgres@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>, 章晨曦 <zhangchenxi@halodbtech.com>, 陈天 <chentian@halodbtech.com>
Date: 2025-08-19T01:31:37Z
Lists: 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&gt;&nbsp;在 2025年8月19日 周二 0:38 写道：

&gt;&nbsp;It doesn't, which is (one reason) why it's just a crude hack.

&gt;&nbsp;A more appropriate solution would be to make plpgsql install

&gt; a shared-cache-invalidation callback that would watch for