Re: Improve LWLock tranche name visibility across backends

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: Sami Imseih <samimseih(at)gmail(dot)com>, Rahila Syed <rahilasyed90(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improve LWLock tranche name visibility across backends
Date: 2025-08-19 17:29:14
Message-ID: aKS0auEl4UUlt7XO@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 19, 2025 at 08:09:53AM +0000, Bertrand Drouvot wrote:
> On Mon, Aug 18, 2025 at 05:53:44PM -0500, Sami Imseih wrote:
>> > (or some other shmem-based
>> > data structure we have yet to introduce, like a dslist/dsarray).
>>
>> This will be an interesting API to invest time in, if there could be more
>> use-cases.
>
> I did a quick check and I did not find current use cases: possible candidates
> could be in ExecParallelHashTableAlloc(), PTIterationArray, PTEntryArray for
> examples but I think they all know the final size upfront so there is no real
> need for dsarray for those).
>
>> I think it's a separate discussion at this point.
>
> OTOH, that would be a valid use case to introduce this new API but I'm not sure
> it's worth it given that the dshash looks good enough for our case (even if not
> ideal though).

IMHO it'd be okay to proceed with dshash for now. It would be pretty easy
to switch to something like a "dslist" in the future.

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2025-08-19 17:31:39 Re: New commitfest app release on August 19th
Previous Message Tomas Vondra 2025-08-19 17:23:24 Re: index prefetching