[MDEV-10846] Running mysqldump backup twice returns error: Table 'mysql.proc' doesn't exist Created: 2016-09-20 Updated: 2016-10-27 Resolved: 2016-10-26 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Data Definition - Procedure, Scripts & Clients |
| Affects Version/s: | 10.1.17, 10.0, 10.1 |
| Fix Version/s: | 10.0.28 |
| Type: | Bug | Priority: | Major |
| Reporter: | Geoff Montee (Inactive) | Assignee: | Alexey Botchkov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | mysqldump | ||
| Issue Links: |
|
||||||||||||||||
| Sprint: | 10.0.28 | ||||||||||||||||
| Description |
|
Before doing anything, I recreated a fresh datadir with the following commands:
And then I took a backup with the following command:
And now watch what happens if I try to load this backup twice:
The error message above says that the error occurs at line 22. The statement at this line is:
Why does the MariaDB think the mysql.proc table doesn't exist at this point? Why does the backup work the first time, but not the second time? The backup works when I run it a third time.
|
| Comments |
| Comment by Elena Stepanova [ 2016-09-25 ] |
|
Reproducible also on 10.0, even on 10.0.10. holyfoot, could you please take a look at it? |
| Comment by Sergey Vojtovich [ 2016-10-21 ] |
|
See also |
| Comment by Alexey Botchkov [ 2016-10-22 ] |
|
Patch proposal: |
| Comment by Alexey Botchkov [ 2016-10-22 ] |
|
The fix itself: and small addition for the test |