pgsql: Make FP_LOCK_SLOTS_PER_BACKEND look like a function - Mailing list pgsql-committers

From Tomas Vondra
Subject pgsql: Make FP_LOCK_SLOTS_PER_BACKEND look like a function
Date
Msg-id E1tpWA4-000m9L-1D@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Make FP_LOCK_SLOTS_PER_BACKEND look like a function

The FP_LOCK_SLOTS_PER_BACKEND macro looks like a constant, but it
depends on the max_locks_per_transaction GUC, and thus can change. This
is non-obvious and confusing, so make it look more like a function by
renaming it to FastPathLockSlotsPerBackend().

While at it, use the macro when initializing fast-path shared memory,
instead of using the formula.

Reported-by: Andres Freund
Discussion: https://postgr.es/m/ffiwtzc6vedo6wb4gbwelon5nefqg675t5c7an2ta7pcz646cg%40qwmkdb3l4ett

Branch
------
master

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

Modified Files
--------------
src/backend/storage/lmgr/lock.c   | 10 +++++-----
src/backend/storage/lmgr/proc.c   |  4 ++--
src/backend/utils/init/postinit.c |  2 +-
src/include/storage/proc.h        |  3 ++-
4 files changed, 10 insertions(+), 9 deletions(-)


pgsql-committers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: pgsql: Generalize hash and ordering support in amapi
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Generalize hash and ordering support in amapi