File: v_metrics.test

package info (click to toggle)
mysql-8.0 8.0.43-3
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 1,273,924 kB
  • sloc: cpp: 4,684,605; ansic: 412,450; pascal: 108,398; java: 83,641; perl: 30,221; cs: 27,067; sql: 26,594; sh: 24,181; python: 21,816; yacc: 17,169; php: 11,522; xml: 7,388; javascript: 7,076; makefile: 2,194; lex: 1,075; awk: 670; asm: 520; objc: 183; ruby: 97; lisp: 86
file content (26 lines) | stat: -rw-r--r-- 933 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
-- source ../include/ps_truncate_all_tables.inc
# Tests for sys schema
# Verify the sys.metrics and sys.metrics_56 views

# TODO: Bug#30760026.
# View metadata updates make the view columns after
# the first server restart different from what they look
# like after an upgrade, because the view meta data update
# triggered by the storing of the DD meta data for the
# underlying entities is done using sql_mode=0, which
# is different from the sql_mode used during CREATE
# (i.e. the default sql_mode).
#
# As a short term fix, to avoid noise from test runs,
# we mask the values that become different in order to
# get deterministic results. This short term fix should
# be removed when the underlying issue is fixed.
--replace_column 3 X 5 X

# Ensure structure changes don't slip in
DESC sys.metrics;

# Make sure view select does not error, but ignore results
--disable_result_log
SELECT * FROM sys.metrics;
--enable_result_log