What action to you take when the deadlock causes the transaction to fail?
Maybe there is something subtle going on there.
> -----Original Message-----
> From: Baron Schwartz [mailto:baron@stripped]
> Sent: Monday, October 23, 2006 10:29 AM
> To: internals@stripped
> Subject: Statement gets written to binlog after deadlock
> We have been having persistent issues with statements causing
> deadlock, yet being
> written to the binlog anyway, thus replicated through to the
> slave, where of course
> there is no deadlock. The error message is "Query caused
> different errors on master
> and slave. Error on master: 'Deadlock found when trying to
> get lock; try restarting
> transaction' (1213), Error on slave: 'no error' (0)"
> I can only find one bug related to this:
> The problem with filing a bug report on it is that it's not
> repeatable. We see it 8 or
> ten times a week, then not at all for several weeks. I don't
> think we can possibly
> file a usable bug report. We have lots of deadlocks, but
> most of them don't cause the
> Does anyone have any ideas about how to solve this issue, or
> create a good bug report
> that won't stagnate? Should we just add comments to the
> existing bug report and hope
> that gains it some attention?
> We're using MySQL's 5.0.21 release.
> Baron Schwartz
> MySQL Internals Mailing List
> For list archives: http://lists.mysql.com/internals
> To unsubscribe: