Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-17232

error codes when decryption fails depend on innodb-stats-persistent

    XMLWordPrintable

Details

    Description

      There different error codes generated when table cannot be encrypted and innodb-stats-persistent is ON/OFF:

      CURRENT_TEST: encryption.innodb-bad-key-change
      mysqltest: At line 45: query 'SELECT * FROM t1' failed with wrong errno 1296: 'Got error 192 'Table encrypted but decryption failed. This could be because correct encryption management plugin is not loaded, used encryption key is not available or encryption method does not match.' from InnoDB', instead of 1932...

      To see the error change innodb-stats-persistent to ON in innodb-bad-key-change.test

      Attachments

        Activity

          People

            marko Marko Mäkelä
            robgolebiowski Robert Golebiowski
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.