File: show_profile.test

package info (click to toggle)
mariadb 1%3A11.8.3-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, 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 (23 lines) | stat: -rw-r--r-- 718 bytes parent folder | download | duplicates (5) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
 
#
# Test for show profiles
# No meaningful check is possible. 
# So it only checks that SET profiling is possible and
# that SHOW PROFILES, SHOW PROFILE FOR QUERY and SHOW PROFILE CPU FOR QUERY
# do not cause syntax errors. It also increases code coverage for sql_profile.cc

# Tests will be skipped for the view protocol because the view protocol creates 
# an additional util connection and other statistics data
-- source include/no_view_protocol.inc

--source include/have_profiling.inc
--disable_ps2_protocol
SET profiling = 1;
SELECT 1;
--replace_column 2 #
SHOW PROFILES;
--disable_result_log
SHOW PROFILE FOR QUERY 1;
SHOW PROFILE CPU FOR QUERY 1;
--enable_result_log 
SET profiling = 0;
--enable_ps2_protocol