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 aKOeMUjcv9Gozyyg@nathan
Whole thread Raw
In response to Re: Improve LWLock tranche name visibility across backends  (Sami Imseih <samimseih@gmail.com>)
Responses Re: Improve LWLock tranche name visibility across backends
List pgsql-hackers
On Mon, Aug 18, 2025 at 01:06:42PM -0500, Sami Imseih wrote:
> Attached is v10,

I've been staring at the latest patch for a bit, and I'm a bit concerned
at how much complexity it adds.  I think it's a good idea to keep a local
array of tranche names indexed by tranche ID, but the code for managing the
list of DSA pointers scares me.  I know we were trying to avoid using
dshash earlier, if for no other reason than it's perhaps not the best data
structure for the job, but ISTM we'd eliminate a lot of complexity if we
offloaded the shmem pieces to a dshash table (or some other shmem-based
data structure we have yet to introduce, like a dslist/dsarray).  WDYT?

-- 
nathan



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Improve hash join's handling of tuples with null join keys
Next
From: Sami Imseih
Date:
Subject: Re: shmem_startup_hook called twice on Windows