pgsql: Revert recent change to RequestNamedLWLockTranche(). - Mailing list pgsql-committers

From Nathan Bossart
Subject pgsql: Revert recent change to RequestNamedLWLockTranche().
Date
Msg-id E1uuGgD-000WGv-37@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
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

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/d814d7fc3d5257ae258b502229fc7ca97c97270a

Modified Files
--------------
src/backend/storage/lmgr/lwlock.c | 18 ++++++++++++------
1 file changed, 12 insertions(+), 6 deletions(-)


pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: Clean up newly added guc_tables.inc.c
Next
From: Michael Paquier
Date:
Subject: pgsql: Change pg_lsn_in_internal() to use soft error reporting