dsm_registry: Add detach and destroy features

so please let me know if I missed on something. Best regards, Sungwoo Chang From 06ddb42e39b3bd0e411a9bc96467ca6797673b8a Mon Sep 17 00:00:00 2001 From: swchangdev Date: Fri, 14 Mar 2025 10:00:12 +0900 Subject: [PATCH] Add detach and destroy feature to dsm_registry --- src/backend/sto

Re: dsm_registry: Add detach and destroy features

There was a minor typo in the test module. I built and ran the test_dsm_registry extension before submitting the patch but perhaps it got mixed up with an older version. From 06ddb42e39b3bd0e411a9bc96467ca6797673b8a Mon Sep 17 00:00:00 2001 From: swchangdev Date: Fri, 14 Mar 2025 10:00:12 +0900 Su

Re: dsm_registry: Add detach and destroy features

5D3E-81C5-4135-95BB-D414204A0AB4%40gmail.com > [1] https://commitfest.postgresql.org/ Thanks for the heads up. I will add an entry to the commitfest as you advised. Best regards, Sungwoo Chang

Re: dsm_registry: Add detach and destroy features

Regression test failed because I didn't add an extra new line in the expected file. 2025년 3월 17일 (월) 오전 9:55, Sungwoo Chang 님이 작성: > > There was a minor typo in the test module. I built and ran the > test_dsm_registry extension before submitting the patch but perhaps it > got

Re: like pg_shmem_allocations, but fine-grained for DSM registry ?

that note, the attributes you mentioned (backend_pid, is_pinned, and created_at) will be nice information to have for users to decide which entry to detach or destroy. Especially, is_pinned will be crucial because you cannot unpin the dsm segment twice. Best regards, Sungwoo Chang 2025년 3월 15일 (토

Re: like pg_shmem_allocations, but fine-grained for DSM registry ?

ged, and we can continue the discussion from that point on. Best regards, Sungwoo Chang 2025년 3월 19일 (수) 14:43, Florents Tselai 님이 작성: > > > On Wed, Mar 19, 2025, 05:46 Sungwoo Chang wrote: > >> Hi, >> >> I made a patch that adds Detach and Destroy functions for dsm regi