Uploaded image for project: 'Percona Server'
  1. Percona Server
  2. PS-5803

innodb_redo_log_encrypt does not behave correctly with SET PERSIST

    Details

    • Type: Bug
    • Status: Done
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: 8.0.16-7
    • Fix Version/s: 8.0.16-7
    • Component/s: None

      Description

      While testing PR-4556, below scenario was executed

      1. Set current value of innodb-redo-log as master_key
      2. 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

        Smart Checklist

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  zsolt.parragi Zsolt Parragi
                  Reporter:
                  mohit.joshi Mohit Joshi
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - Not Specified
                    Not Specified
                    Logged:
                    Time Spent - 6 hours
                    6h