pgsql: Add a small cache of locks owned by a resource owner in Resource - Mailing list pgsql-committers

From Heikki Linnakangas
Subject pgsql: Add a small cache of locks owned by a resource owner in Resource
Date
Msg-id E1ShgWz-00013h-Ve@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Add a small cache of locks owned by a resource owner in ResourceOwner.

This speeds up reassigning locks to the parent owner, when the transaction
holds a lot of locks, but only a few of them belong to the current resource
owner. This is particularly helps pg_dump when dumping a large number of
objects.

The cache can hold up to 15 locks in each resource owner. After that, the
cache is marked as overflowed, and we fall back to the old method of
scanning the whole local lock table. The tradeoff here is that the cache has
to be scanned whenever a lock is released, so if the cache is too large,
lock release becomes more expensive. 15 seems enough to cover pg_dump, and
doesn't have much impact on lock release.

Jeff Janes, reviewed by Amit Kapila and Heikki Linnakangas.

Branch
------
master

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

Modified Files
--------------
src/backend/storage/lmgr/lock.c       |  154 ++++++++++++++++++++++-----------
src/backend/utils/resowner/resowner.c |   95 ++++++++++++++++++++-
src/include/storage/lock.h            |    4 +-
src/include/utils/resowner.h          |    5 +
4 files changed, 205 insertions(+), 53 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Remove incomplete/incorrect support for zero-column foreign keys
Next
From: Alvaro Herrera
Date:
Subject: pgsql: Repair comment mangled by a pgindent run long ago