myisam tables are not locked during incremental backup
Bug #771981 reported by
Valentine Gostev
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Critical
|
Valentine Gostev | ||
1.6 |
Fix Released
|
High
|
Alexey Kopytov | ||
2.0 |
Fix Released
|
Critical
|
Valentine Gostev |
Bug Description
When we are running incremental backup with innobackupex MyISAM tables are not locked, even if we do not specify option --no-lock
364 if (!$option_
<snip>
374 mysql_lockall() if !$option_no_lock;
375
376 }
Related branches
lp:~percona-dev/percona-xtrabackup/bugfix759701
- Valentine Gostev (community): Approve (qa)
-
Diff: 62 lines (+19/-23)1 file modifiedinnobackupex (+19/-23)
lp:~akopytov/percona-xtrabackup/bug771981-1.6
- Stewart Smith (community): Approve
-
Diff: 26 lines (+3/-6)1 file modifiedinnobackupex (+3/-6)
description: | updated |
Changed in percona-xtrabackup: | |
importance: | Undecided → Critical |
assignee: | nobody → Valentine Gostev (core-longbow) |
tags: | added: innobackupex |
Changed in percona-xtrabackup: | |
status: | Triaged → Fix Committed |
Changed in percona-xtrabackup: | |
status: | Fix Committed → Fix Released |
Changed in percona-xtrabackup: | |
assignee: | nobody → Valentine Gostev (longbow) |
To post a comment you must log in.
This also causes that slave info file is not written when --slave-info specified, because write_slave_info() subroutine is called from mysql_lockall()