Registering LWTRANCHE_PARALLEL_HASH_JOIN - Mailing list pgsql-hackers

From Thomas Munro
Subject Registering LWTRANCHE_PARALLEL_HASH_JOIN
Date
Msg-id CAEepm=1WM=02cKT7hinnx8xRhN2QdF+WfE6gk5oMPorwLi+XiA@mail.gmail.com
Whole thread Raw
Responses Re: Registering LWTRANCHE_PARALLEL_HASH_JOIN
List pgsql-hackers
Hi,

I forgot to register a display name for LWTRANCHE_PARALLEL_HASH_JOIN,
the tranche ID used by the LWLock that Parallel Hash uses when handing
out chunks of memory.  Please see attached.

It's rare for this LWLock to show up in pg_stat_activity, but if you
stick pg_usleep(10000) into ExecParallelHashTupleAlloc() after the
lock is acquired (the slow path where a new 32KB chunk is needed) and
run some parallel hash joins, then you'll see that pg_stat_activity
reports that as "extension" in unpatched master.

-- 
Thomas Munro
http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly
Next
From: Peter Geoghegan
Date:
Subject: Re: JIT compiling with LLVM v9.0