Back to bug 1300621

Who When What Removed Added
Rupesh Patel 2016-01-21 10:00:44 UTC Priority unspecified urgent
Honza Horak 2016-01-21 10:14:52 UTC CC hhorak
Filip Krska 2016-01-21 13:44:20 UTC CC fkrska, jdornak
Flags needinfo?(jdornak)
Baptiste AGASSE 2016-01-21 14:01:27 UTC CC baptiste.agasse
Jakub Dorňák 2016-01-22 08:56:16 UTC Flags needinfo?(jdornak)
Troels Arvin 2016-01-25 08:35:21 UTC CC troels
Filip Krska 2016-01-26 09:22:53 UTC Keywords Patch
Marcel Kolaja 2016-01-27 13:57:37 UTC CC mkolaja
Jakub Prokes 2016-01-28 17:00:57 UTC CC jprokes
Tomas Hoger 2016-02-02 08:21:52 UTC CC thoger
Jakub Dorňák 2016-02-02 10:28:47 UTC Status NEW MODIFIED
Marcel Kolaja 2016-02-02 13:35:18 UTC Blocks 1303946
Marcel Kolaja 2016-02-02 13:35:56 UTC Keywords ZStream
Lenka Špačková 2016-02-10 15:12:45 UTC CC lkuprova
Jakub Dorňák 2016-02-11 10:45:26 UTC Doc Text Cause:
Race condition may occur when more than one INSERT is executed concurrently on a non-empty InnoDB table with an AUTO_INCREMENT PK immediately after MySQL start up.

Consequence:
One of the concurrent INSERTs fails with Duplicate key error.

Fix:
Applied patch prevents such race condition.

Result:
Each of the concurrent INSERTs gets unique PK.
Lenka Špačková 2016-02-12 05:35:54 UTC Doc Text Cause:
Race condition may occur when more than one INSERT is executed concurrently on a non-empty InnoDB table with an AUTO_INCREMENT PK immediately after MySQL start up.

Consequence:
One of the concurrent INSERTs fails with Duplicate key error.

Fix:
Applied patch prevents such race condition.

Result:
Each of the concurrent INSERTs gets unique PK.
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.
Branislav Blaškovič 2016-04-08 08:46:51 UTC CC bblaskov
errata-xmlrpc 2016-05-09 17:24:58 UTC Status MODIFIED ON_QA
Jakub Dorňák 2016-06-02 13:06:35 UTC Fixed In Version mariadb-5.5.44-3.el7
errata-xmlrpc 2016-09-28 19:49:26 UTC Status ON_QA VERIFIED
errata-xmlrpc 2016-11-02 12:38:56 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-11-03 20:46:29 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-11-03 16:46:29 UTC

Back to bug 1300621