pgsql: Code cleanup in the wake of recent LWLock refactoring.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Code cleanup in the wake of recent LWLock refactoring.
Date: 2016-02-10 15:12:53
Message-ID: E1aTWRp-0001Ss-Vv@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Code cleanup in the wake of recent LWLock refactoring.

As of commit c1772ad9225641c921545b35c84ee478c326b95e, there's no
longer any way of requesting additional LWLocks in the main tranche,
so we don't need NumLWLocks() or LWLockAssign() any more. Also,
some of the allocation counters that we had previously aren't needed
any more either.

Amit Kapila

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/79a7ff0fe56ac9d782b0734ebb0e7a5299015e58

Modified Files
--------------
src/backend/storage/lmgr/lwlock.c | 89 ++++++++-------------------------------
src/include/storage/lwlock.h | 2 -
2 files changed, 17 insertions(+), 74 deletions(-)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2016-02-10 16:08:43 Re: pgsql: Code cleanup in the wake of recent LWLock refactoring.
Previous Message Robert Haas 2016-02-10 13:18:18 pgsql: postgres_fdw: Remove unnecessary variable.

Browse pgsql-hackers by date

  From Date Subject
Next Message David Steele 2016-02-10 15:16:00 Re: Updated backup APIs for non-exclusive backups
Previous Message Stephen Frost 2016-02-10 14:44:36 Re: Updated backup APIs for non-exclusive backups