pgsql: Rename MAX_NAMED_TRANCHES to MAX_USER_DEFINED_TRANCHES

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Rename MAX_NAMED_TRANCHES to MAX_USER_DEFINED_TRANCHES
Date: 2026-03-26 21:46:49
Message-ID: E1w5sXQ-001b9C-38@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Rename MAX_NAMED_TRANCHES to MAX_USER_DEFINED_TRANCHES

The "named tranches" term is a little confusing. In most places it
refers to tranches requested with RequestNamedLWLockTranche(), even
though all built-in tranches and tranches allocated with
LWLockNewTrancheId() also have a name. But in MAX_NAMED_TRANCHES, it
refers to tranches requested with either RequestNamedLWLockTranche()
or LWLockNewTrancheId(), as it's the maximum of all of those in total.

The "user defined" term is already used in
LWTRANCHE_FIRST_USER_DEFINED, so let's standardize on that to mean
tranches allocated with either RequestNamedLWLockTranche() or
LWLockNewTrancheId().

Reviewed-by: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Reviewed-by: Sami Imseih <samimseih(at)gmail(dot)com>
Discussion: https://www.postgresql.org/message-id/47aaf57e-1b7b-4e12-bda2-0316081ff50e@iki.fi

Branch
------
master

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

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

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2026-03-26 22:03:58 pgsql: Move ShmemIndexLock into ShmemAllocator
Previous Message Tom Lane 2026-03-26 21:27:49 pgsql: Doc: declutter CREATE TABLE synopsis.