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

Persistent AUTO_INCREMENT for InnoDB

Details

    • 10.2.4-1

    Description

      The current auto_increment behavior in the InnoDB engine is sub-optimal. As it currently functions, the auto_increment value is stored until the server shuts down or resets, and then is rebuilt based on values in the table when it starts up again. Furthermore, in 5.6 this ought to become even worse, because tables can be evicted from the InnoDB data dictionary cache. We may get a too low auto-increment value even without shutdown/restart. When a table is evicted, InnoDB will forget the current auto-increment value, and it will do SELECT MAX(auto_inc_column) next time when the table is accessed.

      Attachments

        Issue Links

          Activity

            Transition Time In Source Status Execution Times
            Jan Lindström (Inactive) made transition -
            Open In Progress
            34d 18h 38m 1
            Jan Lindström (Inactive) made transition -
            In Progress Stalled
            200d 5h 37m 1
            Marko Mäkelä made transition -
            Stalled In Progress
            742d 18h 48m 1
            Marko Mäkelä made transition -
            In Progress In Review
            6h 27m 1
            Jan Lindström (Inactive) made transition -
            In Review Stalled
            1d 13h 57m 1
            Marko Mäkelä made transition -
            Stalled Closed
            13d 5h 35m 1

            People

              marko Marko Mäkelä
              jplindst Jan Lindström (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              12 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.