mirror of
https://github.com/MariaDB/server.git
synced 2025-01-31 02:51:44 +01:00
93d495f365
With MDEV-15132 in MariaDB 10.3.5, InnoDB no longer writes the transaction identifier to the TRX_SYS page. The information is only written to undo log headers and sometimes rollback segment headers. Because the setting innodb_force_recovery=5 will skip reading any of those pages, the maximum transaction identifier will no longer be determined. innobase_map_isolation_level(): Always report READ UNCOMMITTED if innodb_force_recovery has been set to 5 or more, or innodb_read_only is set. This will avoid errors reported by lock_check_trx_id_sanity() and ReadView::check_trx_id_sanity(). lock_clust_rec_cons_read_sees(): Do not check for innodb_read_only, now that innobase_map_isolation_level() will guarantee that no read view will be created or used. row_search_mvcc(): Do not check for innodb_force_recovery<5, now that innobase_map_isolation_level() will guarantee that no read view will be created or used.
69 lines
1.6 KiB
Text
69 lines
1.6 KiB
Text
connect con1, localhost, root;
|
|
CREATE TABLE t(a INT PRIMARY KEY) ENGINE=InnoDB;
|
|
INSERT INTO t VALUES(1);
|
|
BEGIN;
|
|
INSERT INTO t VALUES(2);
|
|
UPDATE t SET a=20 WHERE a=2;
|
|
connect con2, localhost, root;
|
|
# Normal MariaDB shutdown would roll back the above transaction.
|
|
# We want the transaction to remain open, so we will kill the server
|
|
# after ensuring that any non-transactional files are clean.
|
|
FLUSH TABLES;
|
|
# Create another transaction that will be recovered as COMMITTED.
|
|
BEGIN;
|
|
SET DEBUG_SYNC='after_trx_committed_in_memory SIGNAL committed WAIT_FOR ever';
|
|
COMMIT;
|
|
connection default;
|
|
SET DEBUG_SYNC='now WAIT_FOR committed';
|
|
# Ensure that the above transactions become durable.
|
|
SET GLOBAL innodb_flush_log_at_trx_commit=1;
|
|
BEGIN;
|
|
INSERT INTO t VALUES(-10000);
|
|
ROLLBACK;
|
|
disconnect con1;
|
|
disconnect con2;
|
|
SELECT * FROM t;
|
|
a
|
|
1
|
|
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
|
|
SELECT * FROM t;
|
|
a
|
|
1
|
|
20
|
|
UPDATE t SET a=3 WHERE a=1;
|
|
# Starting with MariaDB 10.2, innodb_read_only implies READ UNCOMMITTED.
|
|
# In earlier versions, this would return the last committed version
|
|
# (only a=3; no record for a=20)!
|
|
SELECT * FROM t;
|
|
a
|
|
3
|
|
20
|
|
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
|
|
SELECT * FROM t;
|
|
a
|
|
3
|
|
20
|
|
#
|
|
# MDEV-15418 innodb_force_recovery=5 displays bogus warnings
|
|
# about too new transaction identifier
|
|
#
|
|
# With the fix, innodb_force_recovery=5 implies READ UNCOMMITTED.
|
|
SELECT * FROM t;
|
|
a
|
|
3
|
|
20
|
|
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
|
|
SELECT * FROM t;
|
|
a
|
|
3
|
|
20
|
|
SET TRANSACTION ISOLATION LEVEL READ COMMITTED;
|
|
SELECT * FROM t;
|
|
a
|
|
3
|
|
20
|
|
SELECT * FROM t;
|
|
a
|
|
3
|
|
DROP TABLE t;
|
|
FOUND 1 /Rolled back recovered transaction [^0]/ in mysqld.1.err
|