Mysql> INSERT INTO table2 SET data = 'data #2' The second table (table2): mysql> CREATE TABLE table2 LIKE table1 Mysql> INSERT INTO table1 SET data = 'data #1' The first table (table1): mysql> CREATE TABLE table1 ( id INT PRIMARY KEY AUTO_INCREMENT, data VARCHAR(50)) Consider the following two tables in database mydb: mysql> CREATE SCHEMA mydb Let’s play around with a simple example to better understand the effect. Even if innodb_rollback_on_timeout is enabled, when a statement fails in a transaction, ROLLBACK is still a more expensive operation than COMMIT.The failed statement is not being rolled back by default.InnoDB lock wait timeout can cause two major implications: The Effects of a InnoDB Lock Wait Timeout The offensive transaction is waiting for row lock to be released by another transaction.The offensive transaction is not fast enough to commit or rollback the transaction within innodb_lock_wait_timeout duration.The above simply means the transaction has reached the innodb_lock_wait_timeout while waiting to obtain an exclusive lock which defaults to 50 seconds. One of the most popular InnoDB’s errors is InnoDB lock wait timeout exceeded, for example: SQLSTATE: General error: 1205 Lock wait timeout exceeded try restarting transaction

TablePlus 5.6.0 instal