Re: pgsql: Add function to log the memory contexts of specified backend pro
От | Fujii Masao |
---|---|
Тема | Re: pgsql: Add function to log the memory contexts of specified backend pro |
Дата | |
Msg-id | b636ab38-8c55-4deb-a621-8651dcab4ced@oss.nttdata.com обсуждение исходный текст |
Ответ на | Re: pgsql: Add function to log the memory contexts of specified backend pro (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: pgsql: Add function to log the memory contexts of specified backend pro
|
Список | pgsql-hackers |
On 2025/05/01 21:42, Robert Haas wrote: > On Thu, May 1, 2025 at 3:53 AM Fujii Masao <masao.fujii@oss.nttdata.com> wrote: >> Just idea, what do you think about adding a flag to indicate whether >> ProcessLogMemoryContextInterrupt() is currently running? Then, >> when a backend receives a signal and ProcessLogMemoryContextInterrupt() >> is invoked, it can simply return immediately if the flag is already set >> like this: > > I think that something like this could work, but you would need more > than this. Otherwise, if the function errors out, the flag would > remain permanently set. Yes, we need to either use PG_TRY()/PG_FINALLY() or handle the flag as a global variable and reset it in the error handling path. I think using PG_TRY()/PG_FINALLY() is the simpler option. Regards, -- Fujii Masao Advanced Computing Technology Center Research and Development Headquarters NTT DATA CORPORATION
В списке pgsql-hackers по дате отправления: