Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1303946 - Duplicate key with auto increment
Duplicate key with auto increment
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: mariadb (Show other bugs)
7.4
All Linux
urgent Severity urgent
: rc
: ---
Assigned To: Jakub Dorňák
Branislav Blaškovič
: Patch, ZStream
Depends On: 1300621
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-02 08:35 EST by Marcel Kolaja
Modified: 2016-03-31 18:00 EDT (History)
12 users (show)

See Also:
Fixed In Version: mariadb-5.5.47-1.el7_2
Doc Type: Bug Fix
Doc Text:
When more than one INSERT operation was executed concurrently on a non-empty InnoDB table with an AUTO_INCREMENT column defined as a primary key immediately after starting MariaDB, a race condition could occur. As a consequence, one of the concurrent INSERT operations failed with a "Duplicate key" error message. A patch has been applied to prevent the race condition. Now, each row inserted as a result of the concurrent INSERT operations receives a unique primary key, and the operations no longer fail in this scenario.
Story Points: ---
Clone Of: 1300621
Environment:
Last Closed: 2016-03-31 18:00:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:0534 normal SHIPPED_LIVE Moderate: mariadb security and bug fix update 2016-03-31 21:50:48 EDT

  None (edit)
Description Marcel Kolaja 2016-02-02 08:35:18 EST
This bug has been copied from bug #1300621 and has been proposed
to be backported to 7.2 z-stream (EUS).
Comment 10 errata-xmlrpc 2016-03-31 18:00:54 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-0534.html

Note You need to log in before you can comment on or make changes to this bug.