Axel Schwenke wrote:
>
> There are some more pitfalls connected to InnoDBs next-key locking
> algorithm. But this is about locking in general, not deadlocks.

Can the next key locking induce a deadlock on it's own?

I am fairly new to MySQL/innodb. I've been and Oracle DBA for a long
time though. I am seeing deadlocks on one application running on mysql
every few minutes. The two transactions in the deadlock section of
'show engine innodb status' are almost always two DELETE's trying to
delete the same row. I've never seen anything like this in Oracle and
I'm wondering if it has to do with next key locking and the default
isolation level difference between Oracle and MySQL. MySQL uses
repeatable read whereas Oracle used read committed.