Date: Fri, 29 Aug 2025 11:02:02 -0500
From: Nathan Bossart <nathandbossart@gmail.com>
To: Sami Imseih <samimseih@gmail.com>
Cc: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>,
	Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>,
	Rahila Syed <rahilasyed90@gmail.com>,
	pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Improve LWLock tranche name visibility across backends
Message-ID: <aLHO-jh-spXWG1pt@nathan>
References: 
 <CAA5RZ0uYpXw8yTpCPiDAvwt9WtXesKM_vebbCjBm4MQBVnchMw@mail.gmail.com>
 <CAA5RZ0u=Fb8dDdPrEzawYjVqAmYB_PTP4Yy3tV78=_gcvXrjjA@mail.gmail.com>
 <aK4Vr0puSQqPI5vS@nathan>
 <CAA5RZ0v=vvzn4mvejQVA1iFabxSTUQZPDuTCAF0WqA41LKns7g@mail.gmail.com>
 <aK7PyCbPib+/JO2+@ip-10-97-1-34.eu-west-3.compute.internal>
 <CAA5RZ0ve-fHuNYW-ruMwg1y1v7-aCqMm_MiNq1KOdg2Y2-pKDw@mail.gmail.com>
 <aLAFhwpzEwbjiWLG@ip-10-97-1-34.eu-west-3.compute.internal>
 <CAA5RZ0s4ip08Lsk=aYuXGCkBr78jhH=gOau939mhAp-rGuNC3Q@mail.gmail.com>
 <aLCEo0ZMV3vIGRWk@nathan>
 <CAA5RZ0vw-r1qjHw5hUNTzAyCiK3KQ-r+G5ECfWSn+qjdu-fpnw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAA5RZ0vw-r1qjHw5hUNTzAyCiK3KQ-r+G5ECfWSn+qjdu-fpnw@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/aLHO-jh-spXWG1pt%40nathan>
Precedence: bulk

On Thu, Aug 28, 2025 at 05:53:23PM -0500, Sami Imseih wrote:
>> I think this patch set will require reworking the "GetNamedLWLockTranche
>> crashes on Windows in normal backend" patch [0], but AFAICT we can easily
>> adjust it to scan through NamedLWLockTrancheNames instead.
> 
> Except, we will need to turn the char**NamedLWLockTranche into a struct
> that will hold the num_lwlocks as well. Something like. But that is doable.

Ah, right.

> If there is no interest to backpatch [0], maybe we should just make this
> change as part of this patch set. What do you think? I can make this change
> in v18.

I think we should keep that separate.  I don't see any benefit to combining
it, and it'd be good to keep the discussion in a single thread in the
archives for future reference.

-- 
nathan