pgsql: cleanup: Deadlock checker is no longer called from signal handle - Mailing list pgsql-committers

From Heikki Linnakangas
Subject pgsql: cleanup: Deadlock checker is no longer called from signal handle
Date
Msg-id E1vpVxz-00285V-0l@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
cleanup: Deadlock checker is no longer called from signal handler

Clean up a few leftovers from when the deadlock checker was called
from signal handler. We stopped doing that in commit 6753333f55, in
year 2015.

- CheckDeadLock can return a return value directly to the caller,
  there's no need to use a global variable for that.

- Remove outdated comments that claimed that CheckDeadLock "signals
  ProcSleep".

- It should be OK to ereport() from DeadLockCheck now. I considered
  getting rid of InitDeadLockChecking() and moving the workspace
  allocations into DeadLockCheck, but it's still good to avoid doing
  the allocations while we're holding all the partition locks. So just
  update the comment to give that as the reason we do the allocations
  up front.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/73d60ac385a93684f68297ae0ccb8f75bc6f23e1

Modified Files
--------------
src/backend/storage/lmgr/deadlock.c | 10 ++++------
src/backend/storage/lmgr/proc.c     | 28 ++++++++++++++++------------
2 files changed, 20 insertions(+), 18 deletions(-)


pgsql-committers by date:

Previous
From: Álvaro Herrera
Date:
Subject: pgsql: Remove HeapTupleheaderSetXminCommitted/Invalid functions
Next
From: Tom Lane
Date:
Subject: pgsql: Last-minute updates for release notes.