[MDEV-32897] main suite prints extra row due to purge and statistics Created: 2023-11-28  Updated: 2023-12-05  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.4, 10.5, 10.6, 10.11, 11.0, 11.1, 11.2, 11.3
Fix Version/s: 10.4.33, 10.5.24, 10.6.17, 10.11.7, 11.0.5, 11.1.4, 11.2.3

Type: Bug Priority: Major
Reporter: Thirunarayanan Balathandayuthapani Assignee: Thirunarayanan Balathandayuthapani
Resolution: Fixed Votes: 0
Labels: 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/'


Generated at Thu Feb 08 10:34:51 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.