My Oracle Support Banner

UPDATE Leads To Unexpected Next-key Lock On Partitioned Table (Doc ID 2427031.1)

Last updated on APRIL 15, 2020

Applies to:

MySQL Server - Version 5.7 to 8.0 [Release 5.7 to 8.0]
Information in this document applies to any platform.

Symptoms

UPDATE queries leading to unexpected deadlocks on partitioned tables.

Table has identical definition without partition part, but on update operation it has different reaction.

Partition table will lock additional row, while non partition table work properly.

Session 2 locked by session 1.

If remove partition definition, session 2 will not be locked.

Changes

The InnoDB table was recently partitioned. Non-partitioned tables do not have same deadlock.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
 Workaround
 Permanent solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.