File: sxlock_func.test

package info (click to toggle)
mariadb-10.5 1%3A10.5.23-0%2Bdeb11u1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 712,240 kB
  • sloc: ansic: 2,158,658; cpp: 1,843,101; asm: 297,745; perl: 59,967; sh: 53,869; pascal: 38,348; java: 33,919; yacc: 19,639; python: 11,119; xml: 10,126; sql: 10,027; ruby: 8,544; makefile: 6,343; cs: 2,866; lex: 1,205; javascript: 1,037; objc: 80; tcl: 73; awk: 46; php: 22; sed: 16
file content (75 lines) | stat: -rw-r--r-- 2,388 bytes parent folder | download
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
# Performance schema tests, for SX-lock
# Note that only Innodb provides instrumented SX-locks,
# so this test depends largely on the innodb instrumentation.

--source include/not_embedded.inc
--source include/have_perfschema.inc
--source include/have_innodb.inc

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
select name from performance_schema.setup_instruments
where name like "wait/synch/sxlock/%" 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';