File: innodb_row_lock_time_ms.test

package info (click to toggle)
mariadb 1%3A11.8.3-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 772,520 kB
  • sloc: ansic: 2,414,714; cpp: 1,791,394; asm: 381,336; perl: 62,905; sh: 49,647; pascal: 40,897; java: 39,363; python: 20,791; yacc: 20,432; sql: 17,907; xml: 12,344; ruby: 8,544; cs: 6,542; makefile: 6,145; ada: 1,879; lex: 1,193; javascript: 996; objc: 80; tcl: 73; awk: 46; php: 22
file content (61 lines) | stat: -rw-r--r-- 2,067 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
--source include/have_innodb.inc
--source include/count_sessions.inc

CREATE TABLE `t`(`id` INT, PRIMARY KEY(`id`)) ENGINE=InnoDB STATS_PERSISTENT=0;

INSERT INTO t VALUES (1);

SET GLOBAL innodb_monitor_disable="lock_row_lock_time";
SET GLOBAL innodb_monitor_disable="lock_row_lock_time_max";
SET GLOBAL innodb_monitor_reset_all='lock_row_lock_time';
SET GLOBAL innodb_monitor_reset_all='lock_row_lock_time_max';
SET GLOBAL innodb_monitor_enable="lock_row_lock_time";
SET GLOBAL innodb_monitor_enable="lock_row_lock_time_max";

BEGIN;
SELECT * FROM t FOR UPDATE;

# We can't predict (innodb/lock)_row_lock_time_avg value, because it's counted
# as the whole waiting time divided by the amount of waits. The
# corresponding counters in lock_sys can't be reset with any query.

--disable_result_log
SELECT @innodb_row_lock_time_before := variable_value
  FROM information_schema.global_status
  WHERE LOWER(variable_name) = 'innodb_row_lock_time';
--enable_result_log

--connect(con1,localhost,root,,)
SET innodb_lock_wait_timeout = 1;
--error ER_LOCK_WAIT_TIMEOUT
SELECT * FROM t FOR UPDATE;
--disconnect con1

--connection default
COMMIT;

SELECT variable_value - @innodb_row_lock_time_before > 100
  FROM information_schema.global_status
  WHERE LOWER(variable_name) = 'innodb_row_lock_time';
# We can't use 'variable_value - @innodb_row_lock_time_max_before' trick for
# innodb_row_lock_time_max, because we can't reset it, and we don't know the
# initial value at the moment of the test execution.
SELECT  variable_value > 100
  FROM information_schema.global_status
  WHERE LOWER(variable_name) = 'innodb_row_lock_time_max';
SELECT count_reset > 100
  FROM INFORMATION_SCHEMA.INNODB_METRICS
  WHERE NAME='lock_row_lock_time';
SELECT count_reset > 100
  FROM INFORMATION_SCHEMA.INNODB_METRICS
  WHERE NAME='lock_row_lock_time_max';

DROP TABLE t;

--disable_warnings
SET GLOBAL innodb_monitor_enable=default;
SET GLOBAL innodb_monitor_disable=default;
SET GLOBAL innodb_monitor_reset_all=default;
--enable_warnings

--source include/wait_until_count_sessions.inc