summaryrefslogtreecommitdiff
path: root/mysql-test/suite/innodb/t/innodb_bug14676111.test
Commit message (Collapse)AuthorAgeFilesLines
* Merge 5.5 into 10.0Marko Mäkelä2017-03-241-35/+30
|\
| * MDEV-11802 innodb.innodb_bug14676111 fails on buildbotMarko Mäkelä2017-03-241-32/+29
| | | | | | | | | | | | | | | | The test was unnecessarily depending on InnoDB purge, which can sometimes fail to proceed. Let us rewrite the test to use BEGIN;INSERT;ROLLBACK to cause the immediate removal of the desired records.
* | Revert the MDEV-4396 tweak to innodb.innodb_bug14676111.Marko Mäkelä2017-02-201-10/+1
| | | | | | | | MDEV-11802 aims to fix the root cause instead.
* | MDEV-4396: Fix innodb.innodb_bug14676111 test.Jan Lindström2014-11-031-21/+32
|/
* MDEV-4396: Fix sporadic failure of test innodb.innodb_bug14676111unknown2013-04-221-0/+5
| | | | | | | | | | | | The problem was that xtradb has innodb_purge_threads default 1 (plain innodb defaults to 0). The test sets a special debug variable and relies on it to force purge to happen. But when using background purge threads, this does not work, the debug code is not made to handle this, so occasionally the test times out waiting for the purge to occur. Fix by explicitly setting innodb_purgee_threads=0 for this test.
* Bug #14676111 WRONG PAGE_LEVEL WRITTEN FOR UPPER THAN FATHER PAGE AT ↵Yasufumi Kinoshita2012-11-121-0/+128
BTR_LIFT_PAGE_UP() btr_lift_page_up() writes wrong page number (different by -1) for upper than father page. But in almost all of the cases, the father page should be root page, no upper pages. It is very rare path. In addition the leaf page should not be lifted unless the father page is root. Because the branch pages should not become the leaf pages. rb://1336 approved by Marko Makela.