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

INSERT ON DUPLICATE KEY UPDATE + innodb_autoinc_lock_mode=1 broken, fixed in percona

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.5.27, 5.3.8, 5.2.12, 5.1.62
    • Fix Version/s: 5.5.28, 5.3.9
    • Component/s: None
    • Labels:
      None

      Description

      From percona: https://bugs.launchpad.net/percona-server/+bug/1035225

      Concurrent INSERT ... ON DUPLICATE KEY UPDATE statements on a table with
      an AUTO_INCREMENT column may result in spurious duplicate key errors
      (and, as a result, lost data due to some rows being updated rather than
      inserted) with the default value of innodb_autoinc_lock_mode=1.

      Tested on 5.5.27 but 5.3.8 is most probably affected too.

        Attachments

          Activity

            People

            Assignee:
            monty Michael Widenius
            Reporter:
            pomyk Patryk Pomykalski
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Due:
              Created:
              Updated:
              Resolved:

                Git Integration

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