|
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. Because the setting innodb_force_recovery=5 will skip reading any undo logs, the maximum transaction identifier cannot be determined.
Because of this, the following kind of warning messages are bogus and should be suppressed when running with innodb_force_recovery set to 5 or 6:
CURRENT_TEST: innodb.innodb_force_recovery
|
--- /usr/share/mysql-test/suite/innodb/r/innodb_force_recovery.result 2018-02-24 20:33:04.000000000 +0000
|
+++ /dev/shm/var/1/log/innodb_force_recovery.reject 2018-02-25 00:10:34.038752342 +0000
|
@@ -34,7 +34,8 @@
|
# Restart the server with innodb_force_recovery as 5.
|
select * from t2;
|
f1 f2
|
-1 2
|
+Warnings:
|
+Warning 1642 InnoDB: Transaction id in a record of table `test`.`t2` is newer than system-wide maximum.
|
insert into t2 values(2, 3);
|
ERROR HY000: Running in read-only mode
|
alter table t2 add f3 int not null, algorithm=copy;
|
|
mysqltest: Result length mismatch
|
|