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

mysql_upgrade failed to revert innodb_index/table_stats tables column datatype length

Details

    Description

      table_name field in both tables (innodb_table_stats & innodb_index_stats) are increased to 199 from 64 for VARCHAR in 10.2.17
      However, downgrading it back to 10.2.15 didn't changed VARCHAR(199) to VARCHAR(64)

      $ mysql_upgrade --upgrade-system-tables
      		 
       
      		 
      The --upgrade-system-tables option was used, user tables won't be touched.
      		 
       
      		 
      Phase 1/7: Checking and upgrading mysql database
      		 
      Processing databases
      		 
       
      		 
      mysql
      		 
      .
      		 
      mysql.innodb_index_stats OK
      		 
      mysql.innodb_table_stats OK
      		 
      .
      		 
      Phase 7/7: Running 'FLUSH PRIVILEGES'
      		 
      OK

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14637 Latching order violation during btr_cur_pessimistic_delete()

          • Major - Major loss of function.
          • Closed

          Activity

            Descending order - Click to sort in ascending order
            marko Marko Mäkelä added a comment -

            The table definition was corrected as part of the MDEV-14637 fix in MariaDB Server 10.2.17 and 10.3.9.

            marko Marko Mäkelä added a comment - The table definition was corrected as part of the MDEV-14637 fix in MariaDB Server 10.2.17 and 10.3.9.
            elenst Elena Stepanova added a comment -

            mysql_upgrade doesn't downgrade, it's an upgrade script, as the name suggests.

            There is no formal downgrade procedure, and neither is it guaranteed to work between an arbitrary pair of releases – usually it would (between close enough minor releases), but sometimes it won't.

            elenst Elena Stepanova added a comment - mysql_upgrade doesn't downgrade, it's an upgrade script, as the name suggests. There is no formal downgrade procedure, and neither is it guaranteed to work between an arbitrary pair of releases – usually it would (between close enough minor releases), but sometimes it won't.

            People

              Unassigned Unassigned
              muhammad.irfan Muhammad Irfan
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.