mirror of
https://github.com/MariaDB/server.git
synced 2025-07-24 19:42:23 +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
19 lines
495 B
Plaintext
19 lines
495 B
Plaintext
# restart
|
|
#
|
|
# Bug#21801423 INNODB REDO LOG DOES NOT INDICATE WHEN
|
|
# FILES ARE CREATED
|
|
#
|
|
# Bug#21796691 INNODB REDO LOG DOES NOT INDICATE WHEN
|
|
# REDO LOGGING IS SKIPPED
|
|
#
|
|
CREATE TABLE t1 (a INT NOT NULL, b INT UNIQUE) ENGINE=InnoDB;
|
|
INSERT INTO t1 VALUES (1,2);
|
|
ALTER TABLE t1 ADD PRIMARY KEY(a), LOCK=SHARED, ALGORITHM=INPLACE;
|
|
ALTER TABLE t1 DROP INDEX b, ADD INDEX (b), LOCK=SHARED;
|
|
# Kill the server
|
|
# restart
|
|
CHECK TABLE t1;
|
|
Table Op Msg_type Msg_text
|
|
test.t1 check status OK
|
|
DROP TABLE t1;
|