Re: Question on LWLockMode in dsa.c - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: Question on LWLockMode in dsa.c
Date
Msg-id CAFiTN-soqsDw+vpNOEu4fxp_0WZxGrpwwjtpsfcEms-0PBjMiw@mail.gmail.com
Whole thread Raw
In response to Question on LWLockMode in dsa.c  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On Tue, Jan 30, 2024 at 6:24 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>
> Hi,
>
> While working on radix tree patch[1], John Naylor found that dsa.c
> doesn't already use shared locks even in dsa_dump(). dsa_dump() seems
> a pure read-only function so I thought we could use a shared lock mode
> there. Is there any reason to use exclusive mode even in dsa_dump()?
>
> Ultimately, since we're trying to add a new function
> dsa_get_total_size() that just returns
> dsa_area_control.total_segment_size and therefore would also be a
> read-only function, I'd like to find out the correct lock mode there.
>

Doesn't seem like there is any reason for this to be an exclusive lock.

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Anthonin Bonnefoy
Date:
Subject: Re: POC: Extension for adding distributed tracing - pg_tracing
Next
From: Dagfinn Ilmari Mannsåker
Date:
Subject: Re: doc patch: Spell I/O consistently