Re: Improve LWLock tranche name visibility across backends

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Sami Imseih <samimseih@gmail.com>

Cc: Nathan Bossart <nathandbossart@gmail.com>, Andres Freund <andres@anarazel.de>, Bertrand Drouvot <bertranddrouvot.pg@gmail.com>, Rahila Syed <rahilasyed90@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2025-08-22T21:33:55Z

Lists: pgsql-hackers

Sami Imseih <samimseih@gmail.com> writes:
> One point I did not make earlier is that the tranche name lengths will
> need to be as long as we allow in dsm_registry.c.

> #define DSMR_NAME_LEN 128

Huh.  Why is that different from NAMEDATALEN in the first place?

			regards, tom lane

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