File: mysql_upgrade_preparation.inc

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 (26 lines) | stat: -rw-r--r-- 723 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
# Include this in any test using mysql_upgrade

# Can't run test of external client with embedded server
-- source include/not_embedded.inc
# diff in the output, if perfschema is not compiled in
# (sys schema views are missing)
-- source include/have_perfschema.inc
#
# Hack:
#
# If running with Valgrind ($VALGRIND_TEST <> 0) then the resource
# consumption (CPU) for upgrading a large log table will be intense.
# Therefore, truncate the log table in advance and issue a statement
# that should be logged.
#
if ($VALGRIND_TEST)
{
  --disable_query_log
  --disable_result_log
  --disable_abort_on_error
  TRUNCATE TABLE mysql.general_log;
  SELECT 1;
  --enable_abort_on_error
  --enable_result_log
  --enable_query_log
}