Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

InnoDB Locks and Transaction Isolation Level

DZone's Guide to

InnoDB Locks and Transaction Isolation Level

What is the difference between InnoDB locks and transaction isolation level? We’ll discuss it in this post.

· Database Zone ·
Free Resource

Compliant Database DevOps and the role of DevSecOps DevOps is becoming the new normal in application development, and DevSecOps is now entering the picture. By balancing the desire to release code faster with the need for the same code to be secure, it addresses increasing demands for data privacy. But what about the database? How can databases be included in both DevOps and DevSecOps? What additional measures should be considered to achieve truly compliant database DevOps? This whitepaper provides a valuable insight. Get the whitepaper

InnoDB locks and transaction isolation

Recently, I received a question from a user about one of my earlier blog posts. Because it wasn't sent as a comment, I will answer it here. The question:

> I am reading your article:
https://www.percona.com/resources/technical-presentations/troubleshooting-locking-issues-percona-mysql-webinar

> Full table scan locks whole table.

> Some bad select (read) query can do full table scan on InnoDB, does it lock whole table please?

> My understanding was that SELECT (read) blocks another DML only in MyISAM.

To answer this question, we need to understand two different concepts: locking and transaction isolation level.

In the default transaction isolation mode for InnoDB,  REPEATABLE READ and the lower TRANSACTION ISOLATION levels, SELECT  doesn't block any DML unless it uses  SELECT...FOR UPDATE or SELECT...LOCK IN SHARE MODE. On slide 20 (31) of my presentation, I use the  SELECT...FOR UPDATE statement (this is why a lock is seen).

However, if transaction isolation mode is SERIALIZABLE, then  SELECT can block updates. You can see this in the example below:


mysql1> set transaction isolation level serializable;

Query OK, 0 rows affected (0,00sec)

mysql1> begin;

Query OK, 0 rows affected (0,00sec)

mysql1> select * from employees join titles using (emp_no);

c936e6fc4c6cbaf77679ba5013339dff -

443308 rows in set(29,69sec)

mysql2> begin;

Query OK, 0 rows affected (0,00sec)

mysql2> update titles set title = 'Engineer' where emp_no = 15504;

ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction


Regarding the different level locks set by InnoDB, I recommend that you follow the links on slide 37 (67) of the presentation, especially "InnoDB Locking Explained With Stick Figures" by Bill Karwin. InnoDB table locks are also explained very well in this blog post by Peter Zaitsev.

Compliant Database DevOps and the role of DevSecOps DevOps is becoming the new normal in application development, and DevSecOps is now entering the picture. By balancing the desire to release code faster with the need for the same code to be secure, it addresses increasing demands for data privacy. But what about the database? How can databases be included in both DevOps and DevSecOps? What additional measures should be considered to achieve truly compliant database DevOps? This whitepaper provides a valuable insight. Get the whitepaper

Topics:
database ,transactions ,transaction isolation ,innodb ,transaction ,locks

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}