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
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
|
# Performance schema tests, for SX-lock
# Note that only Innodb provides instrumented SX-locks,
# so this test depends largely on the innodb instrumentation.
UPDATE performance_schema.setup_instruments SET enabled = 'NO', timed = 'YES';
UPDATE performance_schema.setup_instruments SET enabled = 'YES'
WHERE name like 'wait/synch/sxlock/%';
TRUNCATE TABLE performance_schema.events_waits_history_long;
TRUNCATE TABLE performance_schema.events_waits_history;
TRUNCATE TABLE performance_schema.events_waits_current;
# Check some SX-locks classes are instrumented
# (exclude instruments that depend on compiling options)
select name from performance_schema.setup_instruments
where name like "wait/synch/sxlock/%"
and name not in
("wait/synch/sxlock/innodb/buf_block_lock",
"wait/synch/sxlock/innodb/buf_block_debug_latch")
order by name;
# Check some SX-locks instances are instrumented
select name from performance_schema.rwlock_instances
where name in
(
'wait/synch/sxlock/innodb/btr_search_latch',
'wait/synch/sxlock/innodb/checkpoint_lock',
'wait/synch/sxlock/innodb/dict_operation_lock',
'wait/synch/sxlock/innodb/trx_i_s_cache_lock',
'wait/synch/sxlock/innodb/trx_purge_latch'
)
order by name;
# Some Innodb payload, to produce data
--disable_warnings
drop table if exists t1;
--enable_warnings
create table t1(a int) engine=innodb;
begin;
insert into t1 values (1), (2), (3);
insert into t1 values (1), (2), (3);
insert into t1 values (1), (2), (3);
commit;
drop table t1;
# Make sure some shared_lock operations have been executed
select operation from performance_schema.events_waits_history_long
where event_name like "wait/synch/sxlock/%"
and operation = "shared_lock" limit 1;
# Make sure some exclusive_lock operations have been executed
select operation from performance_schema.events_waits_history_long
where event_name like "wait/synch/sxlock/%"
and operation = "exclusive_lock" limit 1;
# The following operations are not verified in this test:
# - shared_exclusive_lock
# - try_shared_lock
# - try_shared_exclusive_lock
# - try_exclusive_lock
# because to observe them:
# - there must be an actual code path using the operation
# (this affects try operations, which are not all used)
# - there must be a repeatable scenario to trigger the
# code path, to use as payload in the test script
# Cleanup
UPDATE performance_schema.setup_instruments SET enabled = 'YES', timed = 'YES';
|
