diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2018-01-02 09:25:37 +0200 |
|---|---|---|
| committer | Marko Mäkelä <marko.makela@mariadb.com> | 2018-01-03 11:39:17 +0200 |
| commit | 7a9fee9853c19c1d6d547cd17f87e9bd8f4ebbaa (patch) | |
| tree | b961be224561dd2ddaa1d1eb911a48bbb3070acf /mysql-test/r/ps.result | |
| parent | 6f28f78429da8c63a47286e28fab9a613387497d (diff) | |
| download | mariadb-git-7a9fee9853c19c1d6d547cd17f87e9bd8f4ebbaa.tar.gz | |
MDEV-13568 gcol.innodb_virtual_debug_purge failed in buildbot with wrong result
The InnoDB background tasks can modify tables while LOCK TABLES...WRITE
is in effect. The purge of InnoDB history always worked like this in
MariaDB, but in MySQL 5.7 it sometimes yields to LOCK TABLES.
Also, make gcol.innodb_virtual_index run the purge for an UPDATE
before DROP TABLE is executed.
Diffstat (limited to 'mysql-test/r/ps.result')
0 files changed, 0 insertions, 0 deletions