Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.4, 10.5, 10.6, 10.11, 11.0, 11.1, 11.2, 11.3
-
None
Description
Few test case in main suite prints extra row for metadata lock info table due to
InnoDB background processing of purge record and update of statistics.
CURRENT_TEST: main.backup_stages
|
--- /buildbot/amd64-ubuntu-1804-debug/build/mysql-test/main/backup_stages.result 2022-03-15 03:00:27.000000000 +0000
|
+++ /buildbot/amd64-ubuntu-1804-debug/build/mysql-test/main/backup_stages.reject 2022-03-15 03:47:29.197834923 +0000
|
@@ -23,6 +23,7 @@
|
SELECT LOCK_MODE, LOCK_TYPE, TABLE_SCHEMA, TABLE_NAME FROM information_schema.metadata_lock_info;
|
LOCK_MODE LOCK_TYPE TABLE_SCHEMA TABLE_NAME
|
MDL_BACKUP_START Backup lock
|
+MDL_SHARED Table metadata lock mysql innodb_table_stats
|
connect con2,localhost,root,,;
|
# The connection con2 cannot continue the work of con1 by setting the
|
# next BACKUP STAGE FLUSH.
|
|
mysqltest: Result length mismatch
|
|
- saving '/buildbot/amd64-ubuntu-1804-debug/build/mysql-test/var/13/log/main.backup_stages-innodb/' to '/buildbot/amd64-ubuntu-1804-debug/build/mysql-test/var/log/main.backup_stages-innodb/'
|