diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2020-12-18 19:54:32 +0200 |
|---|---|---|
| committer | Marko Mäkelä <marko.makela@mariadb.com> | 2020-12-18 19:54:32 +0200 |
| commit | 7763eb87f260f8eab1f0edd8e2e1578918e1aec7 (patch) | |
| tree | 1ea7d5ed304f56ccadf44d4571f37073197a40b2 /storage/perfschema/cursor_by_account.cc | |
| parent | 0c23e32d27a11bae6dd38703eba674ef6eeb34f4 (diff) | |
| download | mariadb-git-bb-10.5-corruption.tar.gz | |
MDEV-24449 Crash recovery may fail to apply some logbb-10.5-corruption
We are seeing !buf_pool.any_io_pending() assertion failures
in srv_start() ever since MDEV-21452 in 10.6. But, the
problem appears to be older.
recv_sys_t::apply(): At the end of each batch, wait for
pending reads to complete, so that any pending changes
will have been added to buf_pool.flush_list before we
flush the buffer pool.
io_callback(): Do not invoke read_slots->release()
before the callback function has returned, to ensure
the correct operation of recv_sys_t::apply().
Diffstat (limited to 'storage/perfschema/cursor_by_account.cc')
0 files changed, 0 insertions, 0 deletions