Bug #91204 | Crash on MacOS X when lower_case_table_names=2 and innodb_file_per_table set | ||
---|---|---|---|
Submitted: | 11 Jun 2018 2:55 | Modified: | 18 Jun 2018 12:20 |
Reporter: | Graham Giller | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
Version: | 8.0.11 | OS: | MacOS |
Assigned to: | CPU Architecture: | Any |
[11 Jun 2018 2:55]
Graham Giller
[11 Jun 2018 2:55]
Graham Giller
The .idb file is not missing!
[11 Jun 2018 3:25]
MySQL Verification Team
Thank you for the bug report. See https://bugs.mysql.com/bug.php?id=90695 and below explanation of developer: [2 May 7:29] Ståle Deraas Posted by developer: After initialization, is is not allowed to change this setting. https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_lower_case_tab... So "lower_case_table_names" needs to be set together with --initialize .
[11 Jun 2018 3:33]
Graham Giller
I have never specified lower_case_table_names at all until this instability occurs, and only specified it to stop the system crashing. Initializing a Datadir and restoring a database from a backup file results in an unstable system that crashes. That’s a bug! If it’s not allowed to do something you shouldn’t let the user do it.
[12 Jun 2018 11:19]
Ståle Deraas
Hi Graham, I was a bit fast there. The issue is verified, and we will investigate this further.
[18 Jun 2018 12:20]
Daniel Price
Posted by developer: Fixed as of the upcoming 8.0.13 release, and here's the changelog entry: Table names were not compared in lowercase on macOS with a lowercase_table_names=2 setting, which caused server instability after a restart.