| From: | zengman <zengman(at)halodbtech(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, 章晨曦 <zhangchenxi(at)halodbtech(dot)com>, 陈天 <chentian(at)halodbtech(dot)com> |
| Subject: | Re: Re: When deleting the plpgsql function, release the CachedPlan of the function |
| Date: | 2025-08-19 01:31:37 |
| Message-ID: | tencent_4335FC35086A1BE6369D2B86@qq.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| 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(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Naga Appani | 2025-08-19 01:32:39 | Re: [Proposal] Expose internal MultiXact member count function for efficient monitoring |
| Previous Message | Masahiko Sawada | 2025-08-19 01:17:09 | Re: Logical Replication of sequences |