Bug #1784 ability to log details on all deadlocks
Submitted: 9 Nov 2003 11:44 Modified: 27 Nov 2005 12:43
Reporter: marc slemko
Status: Verified
Category:Server: InnoDB Severity:S4 (Feature request)
Version:4.0.16 OS:Linux (Linux)
Assigned to: Heikki Tuuri Target Version:
Triage: Triaged: D5 (Feature request)

[9 Nov 2003 11:44] marc slemko 
Description:
Right now, SHOW INNODB STATUS shows details of the last deadlock that occurred.  It would
be extremely useful to have a config option that enabled logging this information about
every deadlock that occurs into the mysql.err log (well, stdout I guess).

It would be a huge benefit to be able to characterize why each particular deadlock is
happening so effort can be concentrated on avoiding the most frequent ones or the ones
with the largest transactions.

How to repeat:
n/a

Suggested fix:
n/a
[27 Nov 2005 12:43] Valeriy Kravchuk 
Thank you for a resonable feature request. 

I agree that it will be useful to get information about all deadlocks happened in the
error log. Other RDBMSes (Oracle and IBM Informix, at least) write it to the logs.
[13 Dec 2006 22:46] Valeriy Kravchuk 
Bug #17572 was marked as a duplicate of this one.