pgsql: Cosmetic improvements to group locking.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Cosmetic improvements to group locking.
Date: 2016-02-21 10:17:55
Message-ID: E1aXR5P-00070O-EG@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Cosmetic improvements to group locking.

Reflow text in lock manager README so that it fits within 80 columns.
Correct some mistakes. Expand the README to explain not only why group
locking exists but also the data structures that support it. Improve
comments related to group locking several files. Change the name of a
macro argument for improved clarity.

Most of these problems were reported by Tom Lane, but I found a few
of them myself.

Robert Haas and Tom Lane

Branch
------
master

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

Modified Files
--------------
src/backend/storage/lmgr/README | 104 +++++++++++++++++++++++-------------
src/backend/storage/lmgr/deadlock.c | 21 +++++---
src/backend/storage/lmgr/proc.c | 15 ++++--
src/include/storage/lock.h | 7 +--
src/include/storage/proc.h | 8 +--
5 files changed, 102 insertions(+), 53 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2016-02-21 12:03:08 pgsql: Fix incorrect decision about which lock to take.
Previous Message Robert Haas 2016-02-21 08:51:12 pgsql: postgres_fdw: Avoid sharing list substructure.