mirror of
https://github.com/MariaDB/server.git
synced 2025-07-21 21:22:27 +03:00
a69cf6f07e
In commit 28325b0863
a compile-time option was introduced to disable the macros
DBUG_ENTER and DBUG_RETURN or DBUG_VOID_RETURN.
The parameter name WITH_DBUG_TRACE would hint that it also
covers DBUG_PRINT statements. Let us do that: WITH_DBUG_TRACE=OFF
shall disable DBUG_PRINT() as well.
A few InnoDB recovery tests used to check that some output from
DBUG_PRINT("ib_log", ...) is present. We can live without those checks.
Reviewed by: Vladislav Vaintroub
18 lines
688 B
Plaintext
18 lines
688 B
Plaintext
#
|
|
# Bug#19685095 DO NOT CARE ABOUT UNRESOLVED MLOG_FILE_NAME
|
|
# IF THERE ARE NO OPERATIONS TO APPLY
|
|
#
|
|
SET GLOBAL DEBUG_DBUG='+d,fil_names_write_bogus';
|
|
CREATE TABLE t1(a INT PRIMARY KEY) ENGINE=InnoDB;
|
|
# Kill the server
|
|
# restart: --debug=d,innodb_log_abort_1 --innodb-log-files-in-group=1 --innodb-log-file-size=4M
|
|
SELECT * FROM t1;
|
|
ERROR 42000: Unknown storage engine 'InnoDB'
|
|
FOUND 1 /InnoDB: Tablespace 4294967280 was not found at .*, but there were no modifications either/ in mysqld.1.err
|
|
# restart: --debug=d,innodb_log_abort_3 --innodb-log-files-in-group=1 --innodb-log-file-size=4M
|
|
SELECT * FROM t1;
|
|
ERROR 42000: Unknown storage engine 'InnoDB'
|
|
# restart
|
|
# restart
|
|
DROP TABLE t1;
|