Excessive conflicts in FK parent table

Bug #1216805 reported by Seppo Jaakola on 2013-08-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Status tracked in 5.6
5.5
Low
Seppo Jaakola
5.6
Low
Teemu Ollakka
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Status tracked in 5.6
5.5
Fix Released
Undecided
Unassigned
5.6
Fix Released
Undecided
Unassigned

Bug Description

non-unique indexes in a parent table (as referenced by some foreign key constraint), will be included in write set population. i.e. key values in *all* non-unique indexes will be appended in the write set's key set. This can cause excessive multi-master conflicts, especially if the parent table has non-unique indexes with low selectivity.

Optimally only such non-unique indexes, which are referenced in the foreign key constraint would be used in write set population.

Related branches

Changed in codership-mysql:
status: New → In Progress
importance: Undecided → Low
assignee: nobody → Seppo Jaakola (seppo-jaakola)
milestone: none → 5.5.32-23.7.6
Seppo Jaakola (seppo-jaakola) wrote :
Changed in codership-mysql:
status: In Progress → Fix Committed
Changed in percona-xtradb-cluster:
milestone: none → 5.5.33-23.7.6
Changed in percona-xtradb-cluster:
status: New → Fix Committed
Changed in codership-mysql:
status: Fix Committed → Fix Released
Changed in percona-xtradb-cluster:
status: Fix Committed → Fix Released
Teemu Ollakka (teemu-ollakka) wrote :

Fix to 5.5 pushed inhttp://bazaar.launchpad.net/~codership/codership-mysql/wsrep-5.5/revision/3901

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1428

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers