[MDEV-9440] mysqlcheck -A --auto-repair selects wrong database when trying to repair broken table - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Fixed
Affects Version/s: 10.1.10, 5.5, 10.0, 10.1
Fix Version/s: 5.5.51, 10.1.17, 10.0.27
Component/s: Scripts & Clients
Labels:
- regression
Environment:
Debian 8
$ mysqlcheck -V
mysqlcheck Ver 2.7.4-MariaDB Distrib 10.1.10-MariaDB, for debian-linux-gnu (x86_64)

Description

Given 2 databases each with a table called "table":
db1.tableA
db2.tableB

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.
===
Repairing tables
db2.tableA
Error : Table 'db2.tableA' doesn't exist
status : Operation failed
===

Attachments

Issue Links

relates to

MDEV-10005 mysqlcheck doesn't correctly set default database in repair step

Closed

MDEV-10348 mysql_upgrade mixing up table list

Closed

Activity

People

Assignee:: Sergei Golubchik

Reporter:: Lucian Atody

Votes:: 3 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2016-01-20 15:21

Updated:: 2016-08-08 12:13

Resolved:: 2016-08-08 12:13

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.