mariadb/mysql-test/suite/mariabackup/alter_copy_excluded.result
Marko Mäkelä e1c953ef23 MDEV-25989 Crash (or hang) on startup after restoring backup
If an ALTER TABLE that affected a table with FULLTEXT INDEX was
in progress while a backup was made, InnoDB would crash or hang
during the first startup after restoring the backup,
while trying to drop the #sql-alter- table for the DDL operation.

drop_garbage_tables_after_restore(): Invoke dict_sys.unlock()
before invoking the FTS functions. Also, invoke purge_sys.stop_FTS()
in debug builds to silence debug assertions. (Purge is not yet
running at this point.)
2021-06-22 15:25:58 +03:00

24 lines
819 B
Text

# xtrabackup backup
CREATE TABLE t1(i int, t text, fulltext index(t)) ENGINE=InnoDB;
INSERT into t1 values(1,'foo');
connect con2, localhost, root,,;
connection con2;
SET debug_sync='copy_data_between_tables_before_reset_backup_lock SIGNAL go WAIT_FOR after_backup_stage_block_commit' ;
SET debug_sync='now WAIT_FOR after_backup_stage_start';ALTER TABLE test.t1 DROP t, algorithm=COPY;|
connection default;
connection con2;
SET debug_sync='RESET';
disconnect con2;
connection default;
# xtrabackup prepare
# shutdown server
# remove datadir
# xtrabackup move back
# restart
SELECT * FROM t1;
i t
1 foo
DROP TABLE t1;
SELECT * FROM INFORMATION_SCHEMA.innodb_sys_tablespaces WHERE name like '%/#sql%' or name like 'test/%';
SPACE NAME FLAG ROW_FORMAT PAGE_SIZE FILENAME FS_BLOCK_SIZE FILE_SIZE ALLOCATED_SIZE
# restart