[MDEV-11942] BLACKHOLE is no longer active in 10.1 by default, mysql_upgrade not handling the situation Created: 2017-01-30 Updated: 2020-08-25 Due: 2017-03-10 Resolved: 2017-03-10 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Scripts & Clients |
| Affects Version/s: | 10.1.21 |
| Fix Version/s: | 10.1.22, 10.2.5 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Hartmut Holzgraefe | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | contribution | ||
| Environment: |
linux |
||
| Issue Links: |
|
||||||||
| Sprint: | 10.1.22 | ||||||||
| Description |
|
MariaDB 10.1 binary packages no longer come with BLACKHOLE storage engine compiled in, it comes as a loadable plugin now instead, which is not loaded by default. When upgrading a 10.0 instance with a BLACKHOLE table in it mysql_upgrade detects the problem, but doesn't fix it.
Suggested fix: make mysql_upgrade check I_S.TABLES for unknown storage engine messages in TABLE_COMMENTS, and issue appropriate INSTALL [PLUGIN|SONAME] statements for the bundled engine plugins before actually trying to check and repair tables. |
| Comments |
| Comment by Elena Stepanova [ 2017-01-30 ] |
|
"No longer active" is also true for ARCHIVE and FEDERATED. |
| Comment by Hartmut Holzgraefe [ 2017-02-07 ] |
|
Proposed fix: https://github.com/MariaDB/server/pull/304 |
| Comment by Andrii Nikitin (Inactive) [ 2017-02-14 ] |
|
It looks the change was introduced in 10.1.0 as part of https://jira.mariadb.org/browse/MDEV-6248 |