Re: Improve LWLock tranche name visibility across backends

pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed

From: Nathan Bossart <nathandbossart@gmail.com>
To: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Cc: Sami Imseih <samimseih@gmail.com>
Cc: Rahila Syed <rahilasyed90@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Improve LWLock tranche name visibility across backends
Date: Tue, 19 Aug 2025 12:29:14 -0500
Message-ID: <aKS0auEl4UUlt7XO@nathan> (raw)
In-Reply-To: <aKQxUS6rtMzCkEia@ip-10-97-1-34.eu-west-3.compute.internal>
References: <CAA5RZ0vs6T5OVg3Gs768DxO9QYdAc3FpwaMa6rmqn37WOxH91Q@mail.gmail.com>
	<aJyUGUyx8dQxstPz@ip-10-97-1-34.eu-west-3.compute.internal>
	<CAA5RZ0tm6UFuY43-=fB-JtDEten3gA6tMCH1zLv+R9FT=MDApg@mail.gmail.com>
	<CAA5RZ0ukmNd+C1jH4V6BGEea-wmyLxDtDE5QoEtfXd2W5HNHfQ@mail.gmail.com>
	<aKL1w6tczBqsqLiJ@ip-10-97-1-34.eu-west-3.compute.internal>
	<CAA5RZ0uuWWL5z80KEs95Evy9CrQqnR6vY91BmFor5YmEf06j=w@mail.gmail.com>
	<CAA5RZ0vPcUb68h16ueg=A1R4ps=qU74jvG8N2xaX97DAK-E7_A@mail.gmail.com>
	<aKOeMUjcv9Gozyyg@nathan>
	<CAA5RZ0viNsKqjSuJ8fo74SJrf0uMi=igOn5WrtNYmVqYVh5h-w@mail.gmail.com>
	<aKQxUS6rtMzCkEia@ip-10-97-1-34.eu-west-3.compute.internal>

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

view thread (107+ messages)  latest in thread

Message-ID: <aKS0auEl4UUlt7XO@nathan>
Permalink:  ../aKS0auEl4UUlt7XO@nathan/
Also on:    postgresql.org/message-id/aKS0auEl4UUlt7XO@nathan

 ·

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: nathandbossart@gmail.com, bertranddrouvot.pg@gmail.com, samimseih@gmail.com, rahilasyed90@gmail.com
  Subject: Re: Improve LWLock tranche name visibility across backends
  In-Reply-To: <aKS0auEl4UUlt7XO@nathan>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox