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

auto_increment counters changed weirdly after direct 10.1 -> 10.3 upgrade

    XMLWordPrintable

    Details

      Description

      We have another case where after a direct in-place upgrade from MariaDB 10.1 to 10.3, without intermediate upgrade step to 10.2, auto_increment values on InnoDB tables are somewhat messed up.

      This case is somewhat similar, but not equal, to what was reported in MDEV-20357.

      This time the new auto_increment value wasn't the same for all tables, but strangely for all mangled tables seemed to end with a 9, e.g.: 11209, 11309, 11339, 11359, 11399, 11419, 11449, 11469, 11619 ...

      Also for some of the tables the auto_increment counter had gone down, and apparently stayed at the new value even when inserting (via replication) values with an explicit higher value for the auto inc. column. Only after explicit ALTER TABLE ... AUTO_INCREMENT=...current_max_plus_one... the situation was fixed.

      I assume with persistent auto_increment counter only having been added with 10.2, something can go wrong in direct upgrades skipping 10.2, going directly from 10.1 (or earlier?) to 10.3 as whatever is in the storage area now used for the persistent auto_inc counter may get mis-interpreted?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              hholzgra Hartmut Holzgraefe
              Reporter:
              hholzgra Hartmut Holzgraefe
              Votes:
              0 Vote for this issue
              Watchers:
              8 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.