Fwd: dsm_registry: Add detach and destroy features
От | Sungwoo Chang |
---|---|
Тема | Fwd: dsm_registry: Add detach and destroy features |
Дата | |
Msg-id | CAAdDe3NPTmaO4gr-QnvMgMLS71=Lm7LM1_vdaXWtUYEJrEjAjw@mail.gmail.com обсуждение исходный текст |
Ответ на | dsm_registry: Add detach and destroy features (Sungwoo Chang <swchangdev@gmail.com>) |
Ответы |
Re: Fwd: dsm_registry: Add detach and destroy features
|
Список | pgsql-hackers |
---------- Forwarded message --------- 보낸사람: Sungwoo Chang <swchangdev@gmail.com> Date: 2025년 6월 13일 (금) 오전 8:03 Subject: Re: dsm_registry: Add detach and destroy features To: Nathan Bossart <nathandbossart@gmail.com> > One of the reasons I avoided adding detach/destroy functionality originally > is because this seems difficult to do correctly. How would an extension > ensure that it doesn't end up with one set of backends attached to a new > segment and another attached to an old one that is pending deletion? Sorry for the late response. I used this patch for my extension in a way that you should always detach after you are done using the shmem segment. So the situation you described would happen in a brief moment, but once the extension finishes its task, the shmem segment will be destroyed naturally as all processes detach from it. Would this not be applicable in other extensions?
В списке pgsql-hackers по дате отправления: