mirror of
https://github.com/MariaDB/server.git
synced 2025-06-10 14:42:05 +03:00
a69cf6f07e
In commit 28325b08633372cc343dfcbc41fe252020cf6e6e
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
28 lines
836 B
Plaintext
28 lines
836 B
Plaintext
create table t1(a serial) engine=innoDB;
|
|
set global innodb_encrypt_tables=ON;
|
|
show variables like 'innodb_encrypt%';
|
|
Variable_name Value
|
|
innodb_encrypt_log ON
|
|
innodb_encrypt_tables ON
|
|
innodb_encrypt_temporary_tables OFF
|
|
innodb_encryption_rotate_key_age 2
|
|
innodb_encryption_rotation_iops 100
|
|
innodb_encryption_threads 4
|
|
select count(*) from information_schema.innodb_tablespaces_encryption where current_key_version <> 1;
|
|
count(*)
|
|
0
|
|
set global debug_key_management_version=10;
|
|
select count(*) from information_schema.innodb_tablespaces_encryption where current_key_version <> 10;
|
|
count(*)
|
|
0
|
|
SET GLOBAL innodb_log_checkpoint_now = 1;
|
|
SET GLOBAL innodb_flush_log_at_trx_commit = 1;
|
|
INSERT INTO t1 VALUES(NULL);
|
|
# restart
|
|
set global innodb_encrypt_tables=OFF;
|
|
set global debug_key_management_version=1;
|
|
select * from t1;
|
|
a
|
|
1
|
|
drop table t1;
|