Bug #75194 Use internal name "innodb_redo_log" for the redo log pseudo-tablespace

• Submitted: 12 Dec 2014 15:08
• Modified: 16 Dec 2014 15:32
• Reporter: Marko Mäkelä
• Status: Closed
• Category: MySQL Server: InnoDB storage engine
• Severity: S3 (Non-critical)
• Version: 5.7.6
• OS: Any
• CPU Architecture: Any

[12 Dec 2014 15:08] Marko Mäkelä

Description:
InnoDB creates some tablespaces internally. The names of some these tablespaces start with the "innodb_" prefix in MySQL 5.7:
"innodb_system" and "innodb_temporary"

But, the redo log pseudo-tablespace is being created with a different name, "ib_logfile101".

How to repeat:
./mtr --mem --boot-gdb main.1st
break fil_space_create
c
c
c

Suggested fix:
diff --git a/storage/innobase/srv/srv0start.cc b/storage/innobase/srv/srv0start.cc
index 3b8c7a5..c86be54 100644
--- a/storage/innobase/srv/srv0start.cc
+++ b/storage/innobase/srv/srv0start.cc
@@ -402,7 +402,7 @@ create_log_files(
 	/* Disable the doublewrite buffer for log files, not required */
 
 	fil_space_t*	log_space = fil_space_create(
-		logfilename + dirnamelen, SRV_LOG_SPACE_FIRST_ID,
+		"innodb_redo_log", SRV_LOG_SPACE_FIRST_ID,
 		fsp_flags_set_page_size(0, univ_page_size),
 		FIL_TYPE_LOG);
 	ut_a(fil_validate());

[16 Dec 2014 15:32] Daniel Price

Posted by developer:
 
Fixed as of the upcoming 5.7.6 release, and here's the changelog entry:

The name of the internal pseudo-tablespace that is created for the
"InnoDB" redo log was changed from "ib_logfile101" to "innodb_redo_log".
The new name aligns with other MySQL 5.7 internal tablespace names that
use an "innodb_" prefix.