Re: use LW_SHARED in dsa_get_total_size()

> On Tue, Dec 02, 2025 at 10:31:33AM -0600, Nathan Bossart wrote:
> > On Tue, Dec 02, 2025 at 02:28:29PM +0530, Rahila Syed wrote:
> >> Thank you for highlighting the discussions. I'm unsure about the best
> >> approach here, but I think it would be safe to stay consistent with the
> >> rest of the code in dsa.c, especially since it's unclear that the use of
> >> LW_EXCLUSIVE for reading values in dsa is a mistake.
> >
> > Okay. I switched to LW_EXCLUSIVE and will consider starting a new thread
> > to use LW_SHARED when possible in dsa.c.
>
> Here is a patch that switches to LW_SHARED in dsa_get_total_size() and
> dsa_get_total_size_from_handle().

I think this is a good idea. Exclusive here is not necessarily for the
size lookups.
A specific case I can think of is the work I have been investigating to move
pg_stat_statements query text to shared memory, concurrent backends may
need to check the size of the DSA concurrently, and this will prevent backends
from being blocked when doing so.

If it turns out a backend needs to modify the DSA, they will require
an Exclusive
lock, but that will be after the lookup.

--
Sami Imseih
Amazon Web Services (AWS)