Issue 84 in innotop: feature request: Deadlock clearing transactions set sql_log_bin=0

[inn...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 84 by jon...@gmail.com: feature request: Deadlock clearing
transactions set sql_log_bin=0
http://code.google.com/p/innotop/issues/detail?id=84

using the 'w' key in Deadlocks view will artificially create a deadlock to
wipe the previous info in 'show engine innodb status'. This works and is
very useful, however...

It would be preferred if the transactions to clear the deadlock didn't get
written to the binary log. I do not want them to replicate, in many cases I
don't want to clear deadlock information on slaves, and worst-case it
breaks replication (for example, I didn't have a 'test' schema on the
slaves). IMHO it shouldn't write to binlog by default, but perhaps others
don't agree, so it could be an option?

thanks for consideration,
Jonathan

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[inn...@googlecode.com]

Comment #1 on issue 84 by kenny.g...@percona.com: feature request: Deadlock

clearing transactions set sql_log_bin=0
http://code.google.com/p/innotop/issues/detail?id=84

You're right. I agree with you too. it should not affect other servers.

[inn...@googlecode.com]

Updates:
Status: Fixed

Comment #2 on issue 84 by g...@dakin.be: feature request: Deadlock clearing

transactions set sql_log_bin=0
http://code.google.com/p/innotop/issues/detail?id=84

This issue was closed by revision r113.