mirror of
https://github.com/MariaDB/server.git
synced 2025-07-13 23:08:12 +02:00
d3eefbaa55
The test gcol.gcol_purge would reliably hang on 10.6 on a
Microsoft Windows builder without this adjustment.
A similar adjustment was applied in
commit 3e40f9a7f3
to the tests innodb.dml_purge and innodb.instant_alter_purge.
27 lines
881 B
Text
27 lines
881 B
Text
SET @save_frequency=@@GLOBAL.innodb_purge_rseg_truncate_frequency;
|
|
SET @save_dbug=@@GLOBAL.debug_dbug;
|
|
SET GLOBAL innodb_purge_rseg_truncate_frequency=1;
|
|
CREATE TABLE t1(f1 INT NOT NULL, f2 int not null,
|
|
f3 int generated always as (f2 * 2) VIRTUAL,
|
|
primary key(f1), INDEX (f3))ENGINE=InnoDB;
|
|
connect con1,localhost,root,,,;
|
|
InnoDB 0 transactions not purged
|
|
START TRANSACTION WITH CONSISTENT SNAPSHOT;
|
|
connection default;
|
|
INSERT INTO t1(f1, f2) VALUES(1,2);
|
|
DELETE from t1 where f1 = 1;
|
|
connect con2,localhost,root,,,;
|
|
begin;
|
|
INSERT INTO t1 (f1, f2) VALUES(1,2);
|
|
set global debug_dbug="+d,ib_purge_virtual_index_callback";
|
|
connection con1;
|
|
COMMIT;
|
|
SET GLOBAL innodb_max_purge_lag_wait=1;
|
|
connection con2;
|
|
commit;
|
|
disconnect con1;
|
|
disconnect con2;
|
|
connection default;
|
|
SET GLOBAL innodb_purge_rseg_truncate_frequency=@save_frequency;
|
|
SET GLOBAL debug_dbug=@save_dbug;
|
|
DROP TABLE t1;
|