Bug 1300621 - Duplicate key with auto increment
Summary: Duplicate key with auto increment
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: mariadb
Version: 7.4
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Jakub Dorňák
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Keywords: Patch, ZStream
Depends On:
Blocks: 1303946
TreeView+ depends on / blocked
 
Reported: 2016-01-21 10:00 UTC by Rupesh Patel
Modified: 2016-11-03 20:46 UTC (History)
11 users (show)

(edit)
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.
Clone Of:
: 1303946 (view as bug list)
(edit)
Last Closed: 2016-11-03 20:46:29 UTC


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2595 normal SHIPPED_LIVE Important: mariadb security and bug fix update 2016-11-03 12:11:21 UTC

Description Rupesh Patel 2016-01-21 10:00:18 UTC
Upstream found critical bug in recent releases and they have fixed it here.
https://mariadb.atlassian.net/browse/MDEV-8827

Upstream has fixed it in 5.5.47.

Comment 16 errata-xmlrpc 2016-11-03 20:46:29 UTC
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-2595.html


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