Request a Demo
Home   >   mailing lists

Re: Improve LWLock tranche name visibility across backends - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Improve LWLock tranche name visibility across backends
Date
Msg-id aKTDB5mvSowmC0Lf@nathan
Whole thread Raw
In response to Re: Improve LWLock tranche name visibility across backends  (Andres Freund <andres@anarazel.de>)
Responses Re: Improve LWLock tranche name visibility across backends
List pgsql-hackers
Tree view 
On Tue, Aug 19, 2025 at 02:06:50PM -0400, Andres Freund wrote:
> Possibly stupid question - is it really worth having a dynamic structure here?
> The number of tranches is strictly bound, it seems like it'd be simpler to
> have an array of tranch nmes in shared memory.

Tranches can be allocated post-startup with LWLockNewTrancheId() (e.g.,
autoprewarm).

-- 
nathan

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: RFC: extensible planner state
Next
From: Andrey Borodin
Date:
Subject: Re: VM corruption on standby