mirror of
https://github.com/MariaDB/server.git
synced 2025-07-21 21:22:27 +03:00
fe6eac0cf7
Optimize the test by dropping the table early and by using only one undo log thread, so that purge will be doing more useful work and less busy work of suspending and resuming the worker threads. The test used to cause shutdown timeout on 10.4 on buildbot, and for me locally when using --mysqld=--innodb-sync-debug. With these tweaks, it passes for me with --mysqld=--innodb-sync-debug.
17 lines
594 B
Plaintext
17 lines
594 B
Plaintext
SET GLOBAL innodb_undo_logs = 4;
|
|
SET GLOBAL innodb_undo_log_truncate = 1;
|
|
SET GLOBAL innodb_purge_rseg_truncate_frequency = 1;
|
|
create table t1(keyc int primary key, c char(100)) engine = innodb;
|
|
begin;
|
|
commit;
|
|
begin;
|
|
update t1 set c = 'MariaDB';
|
|
update t1 set c = 'InnoDB';
|
|
set global debug_dbug = '+d,ib_undo_trunc';
|
|
commit;
|
|
drop table t1;
|
|
call mtr.add_suppression("InnoDB: innodb_undo_tablespaces=0 disables dedicated undo log tablespaces");
|
|
call mtr.add_suppression("InnoDB: The transaction log size is too large");
|
|
SET GLOBAL innodb_fast_shutdown=0;
|
|
FOUND 1 /ib_undo_trunc/ in mysqld.1.err
|