[MDEV-9440] mysqlcheck -A --auto-repair selects wrong database when trying to repair broken table Created: 2016-01-20 Updated: 2016-08-08 Resolved: 2016-08-08 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Scripts & Clients |
| Affects Version/s: | 10.1.10, 5.5, 10.0, 10.1 |
| Fix Version/s: | 5.5.51, 10.1.17, 10.0.27 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Lucian Atody | Assignee: | Sergei Golubchik |
| Resolution: | Fixed | Votes: | 3 |
| Labels: | regression | ||
| Environment: |
Debian 8 |
||
| Issue Links: |
|
||||||||||||
| Description |
|
Given 2 databases each with a table called "table": Break table db1.tableA and run `mysqlcheck -A --auto-repair --fast`. mysqlcheck will scan all tables and then should try to repair db1.tableA but instead it remains connected to the last database it checked (in this case db2) and tries to repair table db2.tableA - which does not exist. |
| Comments |
| Comment by Elena Stepanova [ 2016-01-20 ] | ||||||
|
Thanks for the report. The problem appeared in 5.5 tree with the following revision:
Not reproducible on current MySQL 5.5, 5.6, 5.7. | ||||||
| Comment by Elena Stepanova [ 2016-07-08 ] | ||||||
|
See also When fixed, please check the linked issues to make sure all scenarios are covered by the fix. |