Re: Improve LWLock tranche name visibility across backends
От | Nathan Bossart |
---|---|
Тема | Re: Improve LWLock tranche name visibility across backends |
Дата | |
Msg-id | aLHO-jh-spXWG1pt@nathan обсуждение исходный текст |
Ответ на | Re: Improve LWLock tranche name visibility across backends (Sami Imseih <samimseih@gmail.com>) |
Ответы |
Re: Improve LWLock tranche name visibility across backends
|
Список | pgsql-hackers |
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
В списке pgsql-hackers по дате отправления: