mariadb/mysql-test/innodb_unsafe_binlog-master.opt at 0c87a9abcc0b4503122bca1183e02ef244434b51 - mirror/mariadb - May the force be without you: git.fucktheforce.de

mirror/mariadb

mirror of https://github.com/MariaDB/server.git synced 2025-01-27 01:04:19 +01:00

jan 1bd22ab327 Setting a isolation level of the transaction to read committed

weakens the locks for this session similarly like the option
innodb_locks_unsafe_for_binlog. This patch removes almost all
gap locking (used in next-key locking) and makes MySQL to release
the row locks on the rows which does not belong to result set.
Additionally, nonlocking selects on INSERT INTO SELECT,
UPDATE ... (SELECT ...), and CREATE ... SELECT ... use a
nonlocking consistent read. If a binlog is used, then binlog
format should be set to row based binloging to make the execution
of the complex SQL statements.

2006-03-27 05:33:30 +00:00

1 line

No EOL

101 B

Text

Raw Blame History

--innodb_locks_unsafe_for_binlog=true --innodb_lock_wait_timeout=2 --loose_innodb_lock_wait_timeout=2