mirror of
https://github.com/MariaDB/server.git
synced 2025-07-16 08:18:12 +02:00
b4f6b678a6
trx_set_rw_mode(): Check the flag high_level_read_only instead of testing srv_force_recovery (innodb_force_recovery) directly. There is no need to prevent the creation of read-write transactions if innodb_force_recovery=3 is used. Yes, in that mode any recovered incomplete transactions will not be rolled back, but these transactions will continue to hold locks on the records that they have modified. If the new read-write transactions hit conflicts with already existing (possibly recovered) transactions, the lock wait timeout mechanism will work just fine.
39 lines
964 B
Text
39 lines
964 B
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);
|
|
DELETE FROM t WHERE a=2;
|
|
connection default;
|
|
# 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;
|
|
# Ensure that the above incomplete transaction becomes durable.
|
|
SET GLOBAL innodb_flush_log_at_trx_commit=1;
|
|
BEGIN;
|
|
INSERT INTO t VALUES(0);
|
|
ROLLBACK;
|
|
disconnect con1;
|
|
SELECT * FROM t;
|
|
a
|
|
1
|
|
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
|
|
SELECT * FROM t;
|
|
a
|
|
1
|
|
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
|
|
# (empty table)!
|
|
SELECT * FROM t;
|
|
a
|
|
3
|
|
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
|
|
SELECT * FROM t;
|
|
a
|
|
3
|
|
SELECT * FROM t;
|
|
a
|
|
3
|
|
DROP TABLE t;
|