1. 11 Sep, 2015 4 commits
  2. 10 Sep, 2015 3 commits
  3. 09 Sep, 2015 4 commits
  4. 08 Sep, 2015 9 commits
  5. 07 Sep, 2015 6 commits
  6. 06 Sep, 2015 5 commits
  7. 05 Sep, 2015 4 commits
  8. 04 Sep, 2015 5 commits
    • Jan Lindström's avatar
      MDEV-8750: Server crashes in page_cur_is_after_last on altering table using a wrong encryption key · e04723d7
      Jan Lindström authored
      Analysis: Server tried to continue reading tablespace using a cursor after
      we had resolved that pages in the tablespace can't be decrypted.
      
      Fixed by addind check is tablespace still encrypted.
      e04723d7
    • Jan Lindström's avatar
      MDEV-8588: Assertion failure in file ha_innodb.cc line 21140 if at least... · 7e916bb8
      Jan Lindström authored
         MDEV-8588: Assertion failure in file ha_innodb.cc line 21140 if at least one encrypted table exists and encryption service is not available
      
          Analysis: Problem was that in fil_read_first_page we do find that
          table has encryption information and that encryption service
          or used key_id is not available. But, then we just printed
          fatal error message that causes above assertion.
      
          Fix: When we open single table tablespace if it has encryption
          information (crypt_data) store this crypt data to the table
          structure. When we open a table and we find out that tablespace
          is not available, check has table a encryption information
          and from there is encryption service or used key_id is not available.
          If it is, add additional warning for SQL-layer.
      7e916bb8
    • Jan Lindström's avatar
      MDEV-8588: Assertion failure in file ha_innodb.cc line 21140 if at least one... · e1978234
      Jan Lindström authored
      MDEV-8588: Assertion failure in file ha_innodb.cc line 21140 if at least one encrypted table exists and encryption service is not available
      
      Analysis: Problem was that in fil_read_first_page we do find that
      table has encryption information and that encryption service
      or used key_id is not available. But, then we just printed
      fatal error message that causes above assertion.
      
      Fix: When we open single table tablespace if it has encryption
      information (crypt_data) store this crypt data to the table
      structure. When we open a table and we find out that tablespace
      is not available, check has table a encryption information
      and from there is encryption service or used key_id is not available.
      If it is, add additional warning for SQL-layer.
      e1978234
    • Sergei Golubchik's avatar
      test failure · e9b6f950
      Sergei Golubchik authored
      e9b6f950
    • Sergei Golubchik's avatar
      6246b4c9