Request a Demo
Home   >   mailing lists

Re: Use LW_SHARED in WakeupWalSummarizer() for WALSummarizerLock lock - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Use LW_SHARED in WakeupWalSummarizer() for WALSummarizerLock lock
Date
Msg-id aKz675ziP-VbINoQ@nathan
Whole thread Raw
In response to Use LW_SHARED in WakeupWalSummarizer() for WALSummarizerLock lock  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: Use LW_SHARED in WakeupWalSummarizer() for WALSummarizerLock lock
List pgsql-hackers
Tree view 
On Mon, Aug 25, 2025 at 03:38:13PM -0700, Masahiko Sawada wrote:
> While reading walsummarizer.c code, I noticed that in
> WakeupWalSummarizer() we acquire the WALSummarizerLock lock in
> LW_EXCLUSIVE mode despite only reading
> WalSummarizerCtl->summarizer_pgprocno. The attached patch uses
> LW_SHARED mode instead. Feedback is very welcome.

You could probably do something similar for WaitForWalSummarization().

-- 
nathan

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: index prefetching
Next
From: Nathan Bossart
Date:
Subject: Re: Improve LWLock tranche name visibility across backends