summaryrefslogtreecommitdiff
path: root/mysql-test
diff options
context:
space:
mode:
authorMarko Mäkelä <marko.makela@mariadb.com>2018-01-22 16:50:20 +0200
committerMarko Mäkelä <marko.makela@mariadb.com>2018-01-22 16:58:13 +0200
commit431607237d0d1438cdc69f5bf5a188253d7549cf (patch)
tree22ef1b0b6d0f67642c6fa09de323a67453acaae5 /mysql-test
parent5e87f49a9927bf3fd0bd9af789bbdd329e4b4416 (diff)
downloadmariadb-git-431607237d0d1438cdc69f5bf5a188253d7549cf.tar.gz
MDEV-12173 "Error: trying to do an operation on a dropped tablespace"
InnoDB is issuing a 'noise' message that is not a sign of abnormal operation. The only issuers of it are the debug function lock_rec_block_validate() and the change buffer merge. While the error should ideally never occur in transactional locking, we happen to know that DISCARD TABLESPACE and TRUNCATE TABLE and possibly DROP TABLE are breaking InnoDB table locks. When it comes to the change buffer merge, the message simply is useless noise. We know perfectly well that a tablespace can be dropped while a change buffer merge is pending. And the code is prepared to handle that, which is demonstrated by the fact that whenever the message was issued, InnoDB did not crash. fil_inc_pending_ops(): Remove the parameter print_err.
Diffstat (limited to 'mysql-test')
0 files changed, 0 insertions, 0 deletions