Skip to content

Commit

Permalink
WL#9290 InnoDB: Support Transparent Data Encryption for Redo Log
Browse files Browse the repository at this point in the history
Followup patch for fixing test case failure of log_encrypt_kill
and log_encrypt2.
  • Loading branch information
Allen Lai committed Jan 6, 2017
1 parent c6b5bd7 commit 8facbb0
Show file tree
Hide file tree
Showing 3 changed files with 2 additions and 5 deletions.
1 change: 0 additions & 1 deletion mysql-test/suite/innodb/r/log_encrypt_2.result
Original file line number Diff line number Diff line change
@@ -1,4 +1,3 @@
SET @@global.keyring_file_data="MYSQL_TMP_DIR/mysecret_keyring2";
CREATE TABLE t1(c1 int) ENGINE=InnoDB ENCRYPTION="Y";
DROP TABLE t1;
DROP TABLE IF EXISTS t1;
Expand Down
5 changes: 1 addition & 4 deletions mysql-test/suite/innodb/t/log_encrypt_2.test
Original file line number Diff line number Diff line change
Expand Up @@ -17,13 +17,10 @@ call mtr.add_suppression("\\[ERROR\\] InnoDB: Can't set redo log tablespace to b
call mtr.add_suppression("You need to use --log-bin to make --binlog-format work");
--enable_query_log

--replace_result $MYSQL_TMP_DIR MYSQL_TMP_DIR
eval SET @@global.keyring_file_data="$MYSQL_TMP_DIR/mysecret_keyring2";
--sleep 2

CREATE TABLE t1(c1 int) ENGINE=InnoDB ENCRYPTION="Y";

--sleep 1

DROP TABLE t1;

# Restart the server with keyring loaded
Expand Down
1 change: 1 addition & 0 deletions mysql-test/suite/innodb/t/log_encrypt_kill.test
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@ call mtr.add_suppression("InnoDB: Starting to delete and rewrite log files.");
call mtr.add_suppression("InnoDB: New log files created, LSN=");
call mtr.add_suppression("InnoDB: Can't set redo log tablespace to be encrypted");
call mtr.add_suppression("InnoDB: Can't set undo log tablespace to be encrypted");
call mtr.add_suppression("Error in Log_event::read_log_event()");
--enable_query_log

let $old_innodb_file_per_table = `SELECT @@innodb_file_per_table`;
Expand Down

0 comments on commit 8facbb0

Please sign in to comment.