File: statement_program_lost_inst.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 (72 lines) | stat: -rw-r--r-- 2,825 bytes parent folder | download | duplicates (4)
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
#-------------------------------------------------------------
# Tests for PERFORMANCE_SCHEMA stored programs instrumentation  
#-------------------------------------------------------------

#
#  Test case to show the behaviour of stored program instrumentation 
#  when values of the system variables performance_schema_max_program_instances & 
#  performance_schema_max_statement_stack are less than the statistics collected. 
#  The status of the lost instrumentation is shown through the status variables
#  performance_schema_program_lost & performance_schema_nested_statement_lost
#  

# Restarting the server at the begining of the test.
# This is to avoid the instrumentation of extra SPs called by MTR 
# These additional stored programs which will be added might cause 
# result content mismatch failure. 

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

let $restart_file= $MYSQLTEST_VARDIR/tmp/mysqld.1.expect;
--write_line wait $restart_file
--shutdown_server 
--source include/wait_until_disconnected.inc
--write_line "restart:--performance_schema_max_program_instances=7 --performance_schema_max_statement_stack=2 --thread_stack=655360" $restart_file
--enable_reconnect
--source include/wait_until_connected_again.inc

--source ../include/start_server_common.inc

# Values of variables server variables
show global variables like "performance_schema_max_program_instances";
show global variables like "performance_schema_max_statement_stack";

--echo ##################### 
--echo # Setup
--echo ##################### 
--source suite/perfschema/include/program_nested_setup.inc 

# Truncate summary table
TRUNCATE performance_schema.events_statements_summary_by_program;
SELECT OBJECT_TYPE, OBJECT_NAME, OBJECT_SCHEMA FROM 
performance_schema.events_statements_summary_by_program 
WHERE OBJECT_SCHEMA='nested_sp' ORDER BY OBJECT_NAME;
# Flush status now
Flush status;
show global status like "%performance_schema_program_lost%";
show global status like "%performance_schema_nested_statement_lost%";

--echo ##################### 
--echo # Executing Queries
--echo ##################### 
--source suite/perfschema/include/program_nested_execution.inc 

--echo ###########################################
--echo # Quering PS statement summary table      #
--echo ########################################### 

SELECT OBJECT_TYPE, OBJECT_NAME, OBJECT_SCHEMA
       FROM performance_schema.events_statements_summary_by_program
       WHERE OBJECT_SCHEMA='nested_sp' ORDER BY OBJECT_NAME;

# Now check the lost status
show global status like "%performance_schema_program_lost%";
show global status like "%performance_schema_nested_statement_lost%";

--echo ##################### 
--echo # Cleanup
--echo ##################### 
--source suite/perfschema/include/program_nested_cleanup.inc