mirror of
https://github.com/MariaDB/server.git
synced 2025-01-17 04:22:27 +01:00
177c0c2a3c
The test itself is not faulty. The testcase timeout problem happens if this IMHO mid size resource (space in vardir, virtual memory, amount of disk I/O) consuming test meets a weak (excessive disk I/O caused by parallel applications or paging) testing box. The modifications: - Move the most time and disk I/O consuming subtest for Bug 1820 into its own script (multi_update2) This will reduce the likelihood that we exceed the testcase timeout. - Replace error numbers with error names - Minor improvements of the formatting -
25 lines
1,016 B
Text
25 lines
1,016 B
Text
DROP TABLE IF EXISTS t1,t2;
|
|
CREATE TABLE t1 ( a INT NOT NULL, b INT NOT NULL) ;
|
|
# The protocolling of many inserts into t1 is suppressed.
|
|
ALTER TABLE t1 ADD INDEX i1(a);
|
|
DELETE FROM t1 WHERE a > 2000000;
|
|
CREATE TABLE t2 LIKE t1;
|
|
INSERT INTO t2 SELECT * FROM t1;
|
|
SELECT 't2 rows before small delete', COUNT(*) FROM t1;
|
|
t2 rows before small delete COUNT(*)
|
|
t2 rows before small delete 2000000
|
|
DELETE t1,t2 FROM t1,t2 WHERE t1.b=t2.a AND t1.a < 2;
|
|
SELECT 't2 rows after small delete', COUNT(*) FROM t2;
|
|
t2 rows after small delete COUNT(*)
|
|
t2 rows after small delete 1999999
|
|
SELECT 't1 rows after small delete', COUNT(*) FROM t1;
|
|
t1 rows after small delete COUNT(*)
|
|
t1 rows after small delete 1999999
|
|
DELETE t1,t2 FROM t1,t2 WHERE t1.b=t2.a AND t1.a < 100*1000;
|
|
SELECT 't2 rows after big delete', COUNT(*) FROM t2;
|
|
t2 rows after big delete COUNT(*)
|
|
t2 rows after big delete 1900001
|
|
SELECT 't1 rows after big delete', COUNT(*) FROM t1;
|
|
t1 rows after big delete COUNT(*)
|
|
t1 rows after big delete 1900001
|
|
DROP TABLE t1,t2;
|