database/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-08-08 11:22:35 +03:00
Code Activity

MDEV-33101 Server crashes when starting the server with innodb-force-recovery=6 and enabling the innodb_truncate_temporary_tablespace_now variable

Browse Source 
The issue is introduced by "MDEV-28699: Shrink temporary tablespaces
without restart". SRV_FORCE_NO_LOG_REDO forces server to read only mode
and we don't initialize temporary tablespace in read only mode.

solution: innodb_truncate_temporary_tablespace_now should be no-op in
read only mode.
This commit is contained in:
mariadb-DebarunBanerjee
2024-01-05 12:20:37 +05:30
parent 63fb478f88
commit 5a58935cb9
5 changed files with 28 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
mysql-test/suite/innodb/r/temp_truncate.result
View File

@@ -1,3 +1,11 @@
# MDEV-33101 Server crashes when starting the server with
# innodb-force-recovery=6 and enabling the
# innodb_truncate_temporary_tablespace_now variable
# restart: --innodb-force-recovery=6
SHOW VARIABLES LIKE "innodb_read_only";
Variable_name Value
innodb_read_only ON
SET GLOBAL innodb_truncate_temporary_tablespace_now=1;
# restart
CREATE TEMPORARY TABLE t1(f1 INT NOT NULL,
f2 INT NOT NULL)ENGINE=InnoDB;