Details
-
Bug
-
Status: Done
-
High
-
Resolution: Fixed
-
8.0.16-7
-
None
Description
While testing PR-4556, below scenario was executed
- Set current value of innodb-redo-log as master_key
- Execute: set persist innodb_redo_log_encrypt=keyring_key;
Observation:
It actually persists the value as master_key and makes an entry in performance_Schema.persisted_variables
I think this is happening because, we are executing the query successfully and issuing a warning. If instead the query had returned an error then it would not have persisted an incorrect value
Attachments
Issue Links
- blocks
-
PS-4556 Implement redo log encryption
-
- Done
-