If the original table is MyISAM and the default engine is Innodb, and the gtid mode is on, there will be error when execute 'LOCK TABLES tbl WRITE, tbl_magic WRITE'. If make the magic cut-over table's engine same with the original table, there will not have this problem.
This commit is contained in:
parent
d5e78e4b58
commit
a11bec1785
@ -701,8 +701,9 @@ func (this *Applier) CreateAtomicCutOverSentryTable() error {
|
|||||||
|
|
||||||
query := fmt.Sprintf(`create /* gh-ost */ table %s.%s (
|
query := fmt.Sprintf(`create /* gh-ost */ table %s.%s (
|
||||||
id int auto_increment primary key
|
id int auto_increment primary key
|
||||||
) comment='%s'
|
) engine=%s comment='%s'
|
||||||
`,
|
`,
|
||||||
|
this.migrationContext.TableEngine,
|
||||||
sql.EscapeName(this.migrationContext.DatabaseName),
|
sql.EscapeName(this.migrationContext.DatabaseName),
|
||||||
sql.EscapeName(tableName),
|
sql.EscapeName(tableName),
|
||||||
atomicCutOverMagicHint,
|
atomicCutOverMagicHint,
|
||||||
|
Loading…
Reference in New Issue
Block a user