Re: Improve LWLock tranche name visibility across backends

Sami Imseih <samimseih@gmail.com>

From: Sami Imseih <samimseih@gmail.com>

To: Rahila Syed <rahilasyed90@gmail.com>, Bertrand Drouvot <bertranddrouvot.pg@gmail.com>

Cc: Nathan Bossart <nathandbossart@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2025-08-08T18:09:29Z

Lists: pgsql-hackers

From this discussion, and the fact that the tranche name could come from
either local or shared memory, I think we should have tests.
So, I am working on adding tests using INJECTION_POINTS.

Some of the tests I have in mind now are:

1/ Does the shared memory grow correctly,
2/ Is the tranche name being returned the correct one
3/ Is the local cache being updated correctly.

I will have an updated patch with the new test
module early next week.

--
Sami

Commits

test_dsa: Avoid leaking LWLock tranches.
- c5c74282f2ea 19 (unreleased) landed
Teach DSM registry to ERROR if attaching to an uninitialized entry.
- b26d76f64327 18.2 landed
- ac2800ddc185 17.8 landed
- 1165a933aab1 19 (unreleased) landed
Add a test harness for the LWLock tranche code.
- 16607718c010 19 (unreleased) landed
Revert recent change to RequestNamedLWLockTranche().
- d814d7fc3d52 19 (unreleased) landed
Move dynamically-allocated LWLock tranche names to shared memory.
- 38b602b0289f 19 (unreleased) landed
Prepare DSM registry for upcoming changes to LWLock tranche names.
- 5487058b56e0 19 (unreleased) landed
Add GetNamedDSA() and GetNamedDSHash().
- fe07100e82b0 19 (unreleased) cited