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

mysql56-temporal-format=off creates incorrect innodb stats tables

Details

    Description

      mysql56-temporal-format had been disabled in MariaDB 10.1.17 environment. This seemed to work fine, but then the following errors around the innodb persistent statistics tables were observed in the MySQL error logs:

      InnoDB: Error: Column last_update in table "mysql"."innodb_table_stats" is INT UNSIGNED NOT NULL but should be BINARY(4) NOT NULL (type mismatch).
      

      I think this is related to mysql56-temporal-format=off - checking the tables I do see "MYSQL_TYPE_TIMESTAMP" rather than MYSQL_TYPE_TIMESTAMP I reenabled this option, recreated just these tables and these log messages went away and the tables are being populated as expected.

      Attachments

        Activity

          andrew.garner Andrew Garner created issue -
          elenst Elena Stepanova made changes -
          Field Original Value New Value
          Labels need_feedback
          elenst Elena Stepanova made changes -
          Status Open [ 1 ] Confirmed [ 10101 ]
          elenst Elena Stepanova made changes -
          Labels need_feedback
          elenst Elena Stepanova made changes -
          Component/s Storage Engine - InnoDB [ 10129 ]
          Component/s Temporal Types [ 11000 ]
          Fix Version/s 10.1 [ 16100 ]
          Assignee Alexander Barkov [ bar ]
          serg Sergei Golubchik made changes -
          Assignee Alexander Barkov [ bar ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 76885 ] MariaDB v4 [ 143893 ]

          People

            Unassigned Unassigned
            andrew.garner Andrew Garner
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

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