Re: When deleting the plpgsql function, release the CachedPlan of the function
От | Vladlen Popolitov |
---|---|
Тема | Re: When deleting the plpgsql function, release the CachedPlan of the function |
Дата | |
Msg-id | b2b1dc06d0f9bd9d178b3190ce51fcd5@postgrespro.ru обсуждение исходный текст |
Ответ на | Re: When deleting the plpgsql function, release the CachedPlan of the function ("章晨曦" <zhangchenxi@halodbtech.com>) |
Ответы |
Re: When deleting the plpgsql function, release the CachedPlan of the function
|
Список | pgsql-hackers |
章晨曦 писал(а) 2025-08-19 12:31: > > I think you misunderstand Man's meaning. In Man's example, the func > cache > neither dropped (will cause memory leak) nor reused. So the question > here: > > 1. Drop the cache when func dropped > 2. Keep the cache and reused when func recreate > I prefer the 2ed solution. > > Regards, > > Jet C.X. ZHANG Hi It is why I am asking - the patch does not have a detail description in text, it is not clear what and why is changed. What do you mean, when speak about function cache? What object or function allocate it? I wrote in my previous email, that function does not have any cache, it deallocates after the execution everything allocated and does not have cache. Cached plans are not function cache, it is the cache of plans for future use by any other functions or simple query with the same generic or custom plan. They all are deallocated at least when user decides to close the connection. Could you clarify, what function cache do you mean? -- Best regards, Vladlen Popolitov.
В списке pgsql-hackers по дате отправления: