File: fn_ps_is_thread_instrumented.test

package info (click to toggle)
mariadb 1%3A11.8.2-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, trixie
  • size: 765,428 kB
  • sloc: ansic: 2,382,827; cpp: 1,803,532; asm: 378,315; perl: 63,176; sh: 46,496; pascal: 40,776; java: 39,363; yacc: 20,428; python: 19,506; sql: 17,864; xml: 12,463; ruby: 8,544; makefile: 6,059; cs: 5,855; ada: 1,700; lex: 1,193; javascript: 1,039; objc: 80; tcl: 73; awk: 46; php: 22
file content (18 lines) | stat: -rw-r--r-- 673 bytes parent folder | download | duplicates (8) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
 
-- source include/not_embedded.inc
# Tests for sys schema
# Verify the sys.ps_is_thread_instrumented() function perfoms as expected

# Passing NULL/nothing should return NULL
SELECT sys.ps_is_thread_instrumented(NULL);

# By default current thread should be instrumented
SELECT sys.ps_is_thread_instrumented(CONNECTION_ID());

# Now toggle our thread to off and re-check
UPDATE performance_schema.threads SET instrumented = 'NO' WHERE processlist_id = CONNECTION_ID();
SELECT sys.ps_is_thread_instrumented(CONNECTION_ID());

# Try some huge number to check unknown connections
SELECT sys.ps_is_thread_instrumented(234623462376);

--source ../include/ps_threads_cleanup.inc