Bug #91377 Can't Initialize MySQl if internal_tmp_disk_storage_engine is set to MYISAM
| Submitted: | 22 Jun 2018 14:11 | Modified: | 1 Feb 2019 10:04 |
|---|---|---|---|
| Reporter: | Hugo Dubois | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Options | Severity: | S2 (Serious) |
| Version: | 8.0.11 | OS: | CentOS (7.2) |
| Assigned to: | CPU Architecture: | x86 | |
| Tags: | regression | ||
[22 Jun 2018 14:11]
Hugo Dubois
[23 Jun 2018 7:02]
MySQL Verification Team
Hello Dubois, Thank you for the report! Thanks, Umesh
[30 Aug 2018 9:11]
Øystein Grøvlen
Posted by developer: Note that in 8.0.11, Bug#82556 should only be a problem if you use BLOB/TEXT/GEOMETRY/JSON. Hence, if the internal temporary tables are only using other data types, there should be no need to set internal_tmp_disk_storage_engine anymore. In upcoming MySQL 8.0.13, new TempTable engine will also support large objects. (See https://mysqlserverteam.com/mysql-8-0-support-for-blobs-in-temptable-engine/) Then, there should be no need to set internal_tmp_disk_storage_engine at all.
[1 Feb 2019 10:04]
Jon Stephens
Fixed in MySQL 8.0.16 by WL#11974, which removes the use of MyISAM for internal temporary tables as well as the internal_tmp_disk_storage_engine system variable. Closed.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.056 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.