Revert recent change to RequestNamedLWLockTranche().
authorNathan Bossart <nathan@postgresql.org>
Thu, 4 Sep 2025 20:34:48 +0000 (15:34 -0500)
committerNathan Bossart <nathan@postgresql.org>
Thu, 4 Sep 2025 20:34:48 +0000 (15:34 -0500)
commitd814d7fc3d5257ae258b502229fc7ca97c97270a
treee3a98b10315ffd13c2ea51475f6d94f9da8d230f
parentf0478149c34dfe02e0f43fc5f832a63a864dc364
Revert recent change to RequestNamedLWLockTranche().

Commit 38b602b028 modified this function to allocate enough space
for MAX_NAMED_TRANCHES (256) requests, which is likely far more
than most clusters need.  This commit reverts that change so that
it first allocates enough space for only 16 requests and resizes
the array when necessary.  While at it, remove the check for too
many tranches from this function.  We can now rely on
InitializeLWLocks() to do that check via its calls to
LWLockNewTrancheId() for the named tranches.

Reviewed-by: Sami Imseih <samimseih@gmail.com>
Discussion: https://postgr.es/m/aLmzwC2dRbqk14y6%40nathan
src/backend/storage/lmgr/lwlock.c