diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2019-03-17 13:33:31 +0200 |
|---|---|---|
| committer | Sergei Golubchik <serg@mariadb.org> | 2019-03-17 13:06:12 +0100 |
| commit | a89ee3cd154a67df2231f034fd8339f9225dbe64 (patch) | |
| tree | 23afed531a4e65ddfc1398ea34b124def4f8a1a0 /mysql-test/main/sp-ucs2.test | |
| parent | 51e48b9f8981986257a1cfbdf75e4fc29a5959c1 (diff) | |
| download | mariadb-git-a89ee3cd154a67df2231f034fd8339f9225dbe64.tar.gz | |
MDEV-18952 CHECK TABLE should use READ UNCOMMITED if innodb_force_recovery>=5
MDEV-15418 changed InnoDB to use the READ UNCOMMITTED isolation level
when the transaction recovery is disabled by setting
innodb_force_recovery to 5 or 6. Alas, CHECK TABLE would still
internally use REPEATABLE READ. If the server was started without
purge running into completion (and resetting all DB_TRX_ID thanks
to MDEV-12288), this would cause errors about any DB_TRX_ID that
had not been reset to 0.
Diffstat (limited to 'mysql-test/main/sp-ucs2.test')
0 files changed, 0 insertions, 0 deletions