summaryrefslogtreecommitdiff
path: root/mysql-test/main/truncate_coverage.test
diff options
context:
space:
mode:
authorMarko Mäkelä <marko.makela@mariadb.com>2020-10-27 15:35:04 +0200
committerMarko Mäkelä <marko.makela@mariadb.com>2020-10-27 15:47:18 +0200
commit42e1815ad850384fad292534665ff61b78dd96f6 (patch)
tree88e1dbc62723abf652911cd73838c0e8797dae01 /mysql-test/main/truncate_coverage.test
parent8761571a71f0d628c5a82abed115e170d63e34c0 (diff)
downloadmariadb-git-42e1815ad850384fad292534665ff61b78dd96f6.tar.gz
MDEV-16952 Introduce SET GLOBAL innodb_max_purge_lag_wait
Let us introduce a dummy variable innodb_max_purge_lag_wait for waiting that the InnoDB history list length is below the user-specified limit. Specifically, SET GLOBAL innodb_max_purge_lag_wait=0; should wait for all history to be purged. This could be useful when upgrading from an older version to MariaDB 10.3 or later, to avoid hitting MDEV-15912. Note: the history cannot be purged if there exist transactions that may see old versions. Reviewed by: Vladislav Vaintroub
Diffstat (limited to 'mysql-test/main/truncate_coverage.test')
0 files changed, 0 insertions, 0 deletions