pgsql: Move TRACE calls into WaitOnLock()

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Move TRACE calls into WaitOnLock()
Date: 2024-11-04 14:21:50
Message-ID: E1t7xxm-0008wE-E6@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Move TRACE calls into WaitOnLock()

LockAcquire is a long and complex function. Pushing more stuff to its
subroutines makes it a little more manageable.

Reviewed-by: Maxim Orlov
Discussion: https://www.postgresql.org/message-id/7c2090cd-a72a-4e34-afaa-6dd2ef31440e@iki.fi

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/6ae0897e42416d8954f0340ba7eca6275ed8c8b7

Modified Files
--------------
src/backend/storage/lmgr/lock.c | 29 ++++++++++++++---------------
1 file changed, 14 insertions(+), 15 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2024-11-04 14:25:01 pgsql: doc: fix typo in mvcc clarification in commit 2fa255ce9b9
Previous Message Alvaro Herrera 2024-11-04 14:19:26 Re: pgsql: Implement pg_wal_replay_wait() stored procedure