mirror of
https://github.com/MariaDB/server.git
synced 2025-06-04 18:03:14 +03:00
796486d19b
The bug was introduced in MariaDB 10.4.0 by commit 0e5a4ac2532c64a545796c787354dc41d61d0e62 but it is good to have a regression test for this scenario in all applicable MariaDB versions. Cover the purge of an undo log record that was written before the completion of ADD SPATIAL INDEX.
14 lines
505 B
Plaintext
14 lines
505 B
Plaintext
SET @saved_frequency = @@GLOBAL.innodb_purge_rseg_truncate_frequency;
|
|
SET GLOBAL innodb_purge_rseg_truncate_frequency = 1;
|
|
CREATE TABLE t1 (g MULTIPOINT NOT NULL) ENGINE=InnoDB;
|
|
INSERT INTO t1 VALUES ('');
|
|
connect purge_control,localhost,root;
|
|
START TRANSACTION WITH CONSISTENT SNAPSHOT;
|
|
connection default;
|
|
DELETE FROM t1;
|
|
ALTER TABLE t1 ADD SPATIAL INDEX (g);
|
|
disconnect purge_control;
|
|
InnoDB 0 transactions not purged
|
|
DROP TABLE t1;
|
|
SET GLOBAL innodb_purge_rseg_truncate_frequency = @saved_frequency;
|