Bug #82957 Remove MRG_MYISAM (MERGE) storage engine
| Submitted: | 12 Sep 2016 19:14 | Modified: | 16 Feb 2021 12:22 |
|---|---|---|---|
| Reporter: | Daniël van Eeden | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: MyISAM storage engine | Severity: | S3 (Non-critical) |
| Version: | 8.0.0 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | merge, myisam | ||
[12 Sep 2016 19:14]
Daniël van Eeden
[13 Sep 2016 0:06]
MySQL Verification Team
Thank you for the bug report.
[6 Feb 2017 7:15]
Simon Mudd
It's odd as I've had comments with various people and I was under the impression there was a desire to remove the merge table support but I have never actually seen any official push in that direction. As most people are moving away from MyISAM merge table access probably makes less sense although since removal of the higher level partitioning there are less alternatives if you are using MyISAM. I would certainly suggest that if there's a desire to remove this then it should be made more visible and suggestions on alternatives should be made.
[27 Oct 2017 12:37]
Daniël van Eeden
Maybe make it an optional storage engine which is disabled by default?
[16 Feb 2021 12:22]
Daniël van Eeden
Maybe something for MySQL 9?
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.053 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.