Missing fake changes MTR tests
Bug #1190648 reported by
Laurynas Biveinis
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
| 5.1 |
Won't Fix
|
Low
|
Unassigned | |||
| 5.5 |
Triaged
|
Low
|
Unassigned | |||
| 5.6 |
Triaged
|
Low
|
Unassigned | |||
| 5.7 |
Invalid
|
Low
|
Unassigned | |||
Bug Description
As a result of code review / Facebook implementation review, the following cases covered in MTR would make sense.
1) A fake changes trx touching > 10000 rows, due to the autocommit that happens then.
2) Missing tests that DML statements fail properly with fake changes enabled, in fact new 5.6 statements / clauses already are suspect that they will crash/fail: DISCARD/IMPORT TABLESPACE. Other statements to test, based on code review suspicions: OPTIMIZE TABLE, SHOW TABLE STATUS).
3) If possible, create a testcase for 5.6 for fake changes / multi-threaded slave interaction, ref the top change in row0ins.cc at https:/
| tags: | added: fake-changes xtradb |
Revision history for this message
| Laurynas Biveinis (laurynas-biveinis) wrote | #1 |
| description: | updated |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #2 |
To post a comment you must log in.
BLOB/TEXT coverage split off to bug 1200162, as such tests are present in the Facebook patch. Keeping this bug for missing tests for both branches.