From 414b9195ffbdc16d8e652fe96a51b6ccf7ad5d47 Mon Sep 17 00:00:00 2001 From: Yuchen Pei Date: Wed, 5 Aug 2026 15:29:07 +1000 Subject: [PATCH] MDEV-40631 Fix view protocol for main.partition_range_interval For the timeout happening in SELECT statements inside a LOCK TABLE / UNLOCK TABLES block, likely caused by lock conflicts in the service connection. For SHOW CREATE TABLE result mismatch, likely caused by the service connection timestamp being the actual time --- mysql-test/main/partition_range_interval.test | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/mysql-test/main/partition_range_interval.test b/mysql-test/main/partition_range_interval.test index d6f3e03d44c02..fc79fcb861049 100644 --- a/mysql-test/main/partition_range_interval.test +++ b/mysql-test/main/partition_range_interval.test @@ -880,7 +880,9 @@ show create table t1; set timestamp= unix_timestamp('2026-05-06 00:00:00'); lock tables v1 write; update v1 set c= date_add(c, interval 3 day); +--disable_view_protocol select * from t1; +--enable_view_protocol show create table t1; unlock tables; @@ -915,7 +917,9 @@ set timestamp= unix_timestamp('2026-05-06 03:00:00'); lock tables t1 write; execute s; execute s; +--disable_view_protocol select * from t1; +--enable_view_protocol show create table t1; unlock tables; drop prepare s; @@ -931,7 +935,9 @@ lock tables t1 write; call sp; set timestamp= unix_timestamp('2026-05-10 05:00:00'); call sp; +--disable_view_protocol select * from t1; +--enable_view_protocol show create table t1; unlock tables; drop procedure sp; @@ -960,7 +966,10 @@ end| delimiter ;| --disable_ps_protocol +# Service connection timestamp is still whatever the actual time is +--disable_view_protocol select * from t2 where d = f(42); +--enable_view_protocol --enable_ps_protocol select * from t1; SHOW CREATE TABLE t1;