Details

    • Type: Admin & Maintenance Task
    • Status: Done
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: 8.0, Not 5.5, Not 5.6, Not 5.7
    • Fix Version/s: 8.0.16-7
    • Component/s: None
    • Labels:
      None

      Description

      Merge MySQL 8.0.16.

      Reconcile our innodb_encrypt_tables system variable with upstream default_table_encryption / table_encryption_privilege_check system variables and TABLE_ENCRYPTION_ADMIN privilege.

      Change tokubackup to use std::regex instead of my_regex

      DONE

      Leave both our and upstream changed page tracking functionalities intact, eventual removal/merge/reimplementation to be decided at PS-5589.

      The upstream MySQL system tablespace (mysql.ibd) encryption support (https://dev.mysql.com/worklog/task/?id=12063) appears to orthogonal with our ability to do the same by --innodb_encrypt_tables=on during bootstrap, and both will co-exist

      Reconcile "InnoDB: Modifying the value of the innodb_undo_log_encrypt variable was not a blocking operation, which could lead to the modification being reverted by a background thread after the operation appeared to have been completed successfully. (Bug #28952870)" (67cab30d82e) with our encryption features

      Verify upstream bug fixes and revert our fixes for them:

      Add testcases for, if not present:

      Look into adding default -DWITH_ROUTER=OFF in Jenkins for faster builds
      Look into adding default -DWITH_MYSQLX=OFF in Jenkins for faster builds (option available in 8.0.11 already, but did not work due to "MySQL Router compilation failed if MySQL was configured with -DWITH_MYSQLX=0. (Bug #28811356)")

        Smart Checklist

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  laurynas.biveinis Laurynas Biveinis (Inactive)
                  Reporter:
                  yura.sorokin Yura Sorokin
                • Votes:
                  2 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 2 weeks, 2 days, 3 hours, 43 minutes
                    2w 2d 3h 43m