Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.3(EOL)
Description
http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest-big/builds/2224
10.3 573c4db57a9b9fc5998bd2a2f1311873 |
innodb.innodb_stats_persistent 'innodb' w2 [ fail ]
|
Test ended at 2018-11-13 22:28:21
|
|
CURRENT_TEST: innodb.innodb_stats_persistent
|
--- /mnt/buildbot/build/mariadb-10.3.11/mysql-test/suite/innodb/r/innodb_stats_persistent.result 2018-11-13 07:59:56.000000000 -0500
|
+++ /mnt/buildbot/build/mariadb-10.3.11/mysql-test/suite/innodb/r/innodb_stats_persistent.reject 2018-11-13 22:28:20.782762345 -0500
|
@@ -67,7 +67,7 @@
|
1 SIMPLE t2 ref val val 4 const 1 Using index
|
SET @saved_frequency = @@GLOBAL.innodb_purge_rseg_truncate_frequency;
|
SET GLOBAL innodb_purge_rseg_truncate_frequency = 1;
|
-InnoDB 0 transactions not purged
|
+InnoDB 30 transactions not purged
|
SET GLOBAL innodb_purge_rseg_truncate_frequency = @saved_frequency;
|
# After COMMIT and purge, the DELETE must show up.
|
EXPLAIN SELECT * FROM t1 WHERE val=4;
|
|
mysqltest: Result length mismatch
|
Attachments
Issue Links
- relates to
-
MDEV-16260 Scale the purge effort according to the workload
- Open
-
MDEV-16952 Introduce SET GLOBAL innodb_max_purge_lag_wait
- Closed
-
MDEV-18878 Purge is slow due to repeatedly looking up missing or discarded table
- Closed
-
MDEV-11802 innodb.innodb_bug14676111 fails in buildbot due to InnoDB purge failing to start when there is work to do
- Closed
-
MDEV-12288 Reset DB_TRX_ID when the history is removed, to speed up MVCC
- Closed
-
MDEV-22958 innodb.instant_alter_debug fails in buildbot with wrong result
- Closed