pgsql: Fix the number of lwlocks needed by the "fast path" lock patch.

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix the number of lwlocks needed by the "fast path" lock patch.
Date: 2011-10-27 19:47:48
Message-ID: E1RJVvY-0006PW-KJ@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2011-10-28 01:29:53 pgsql: Update pg_upgrade testing instructions.
Previous Message Tom Lane 2011-10-27 19:22:05 pgsql: Avoid recursion while processing ELSIF lists in plpgsql.