pgsql: Use macros instead of hardcoded offsets for LWLock initializatio

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Use macros instead of hardcoded offsets for LWLock initializatio
Date: 2020-11-24 03:48:18
Message-ID: E1khPJS-0007or-BC@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Use macros instead of hardcoded offsets for LWLock initialization

This makes the code slightly easier to follow, as the initialization
relies on an offset that overlapped with an equivalent set of macros
defined, which are used in other places already.

Author: Japin Li
Discussion: https://postgr.es/m/MEYP282MB1669FB410006758402F2C3A2B6E00@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/d03d7549b29236e300aceac0c22173cf19acc675

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

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2020-11-24 08:01:02 pgsql: doc: Get rid of unnecessary space character from some index item
Previous Message Tom Lane 2020-11-24 00:11:10 pgsql: Centralize logic for skipping useless ereport/elog calls.