-
- Downloads
Code review for log_lock_waits patch. Don't try to issue log messages from
within a signal handler (this might be safe given the relatively narrow code range in which the interrupt is enabled, but it seems awfully risky); do issue more informative log messages that tell what is being waited for and the exact length of the wait; minor other code cleanup. Greg Stark and Tom Lane
Showing
- doc/src/sgml/config.sgml 13 additions, 6 deletionsdoc/src/sgml/config.sgml
- src/backend/storage/lmgr/deadlock.c 14 additions, 92 deletionssrc/backend/storage/lmgr/deadlock.c
- src/backend/storage/lmgr/lmgr.c 77 additions, 1 deletionsrc/backend/storage/lmgr/lmgr.c
- src/backend/storage/lmgr/proc.c 109 additions, 47 deletionssrc/backend/storage/lmgr/proc.c
- src/backend/utils/misc/guc.c 4 additions, 3 deletionssrc/backend/utils/misc/guc.c
- src/include/storage/lmgr.h 5 additions, 1 deletionsrc/include/storage/lmgr.h
- src/include/storage/lock.h 7 additions, 5 deletionssrc/include/storage/lock.h
Loading
Please register or sign in to comment