Re: Improve LWLock tranche name visibility across backends

> On Tue, Aug 19, 2025 at 03:52:33PM -0500, Sami Imseih wrote:
> > If we limit the tranche name to NAMEDATALEN and also limit the
> > number of tranches an extension can register, we can put this
> > all in static shared memory (We would still need to have a backend local
> > cache to allow lookups to avoid going to shared memory).
>
> I bet we could avoid the local cache by keeping a backend-local copy of
> LWLockCounter that gets updated as needed.

maybe. If we agree to impose limits ( both name length and # of tranches ),
that will allow us to do things a bit different.

If there is agreement on setting limits, may I propose
1024 tranches and NAMEDATALEN. Both seem reasonably sufficient.

--
Sami