pgsql: Fix the number of lwlocks needed by the "fast path" lock patch. - Mailing list pgsql-committers

From Heikki Linnakangas
Subject pgsql: Fix the number of lwlocks needed by the "fast path" lock patch.
Date
Msg-id E1RJVvY-0006PW-KJ@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix the number of lwlocks needed by the "fast path" lock patch. It needs
one lock per backend or auxiliary process - the need for a lock for each
aux processes was not accounted for in NumLWLocks(). No-one noticed,
because the three locks needed for the three aux processes fit into the
few extra lwlocks we allocate for 3rd party modules that don't call
RequestAddinLWLocks() (NUM_USER_DEFINED_LWLOCKS, 4 by default).

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/cbf65509bb59694412286239fe6db409060f8d69

Modified Files
--------------
src/backend/storage/lmgr/lwlock.c |    4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Avoid recursion while processing ELSIF lists in plpgsql.
Next
From: Bruce Momjian
Date:
Subject: pgsql: Update pg_upgrade testing instructions.