mixed CHAR and VARCHAR columns in foreign key definition makes parallel applying fail
Bug #1100496 reported by
Seppo Jaakola
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL patches by Codership |
Fix Released
|
High
|
Seppo Jaakola | |||
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
If foreign key column and corresponding referenced table column are of types CHAR and VARCHAR (or vice versa), then controlling of parallel applying may not work.
Problem is that CHAR columns will be fixed length with space padding in the end and the whole column will be appended as certification key value. For VARCHAR columns only 'effective' characters are append as key value.
Changed in codership-mysql: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Seppo Jaakola (seppo-jaakola) |
Changed in codership-mysql: | |
milestone: | none → 5.5.29-23.7.1 |
Changed in percona-xtradb-cluster: | |
milestone: | none → 5.5.30-23.7.4 |
status: | New → Fix Released |
To post a comment you must log in.
Fix pushed in revision: http:// bazaar. launchpad. net/~codership/ codership- mysql/5. 5-23/revision/ 3841
The fix will run FK test for child table delete (and index update) operations, and use parent table index directly for populating certification keys for wsrep provider. Note, this is excessive FK test, not normally run.