diff options
| author | Marko Mäkelä <marko.makela@mariadb.com> | 2017-09-01 22:07:43 +0300 |
|---|---|---|
| committer | Marko Mäkelä <marko.makela@mariadb.com> | 2017-09-01 22:07:43 +0300 |
| commit | 1136c8d366a6ad7b8d487194fb01c0a5bb072220 (patch) | |
| tree | 782137843ea7d432f1440ae373e3702ad358e2c3 /scripts | |
| parent | b660584b108544cd36b734d724b2f3a6bc98ebfa (diff) | |
| download | mariadb-git-1136c8d366a6ad7b8d487194fb01c0a5bb072220.tar.gz | |
Follow-up to MDEV-13570 Assertion failure !srv_read_only_mode in --innodb-read-only shutdown when buf_resize_thread is active
logs_empty_and_mark_files_at_shutdown(): Actually skip the debug assertion
when the buf_resize_thread is active. The previous fix skipped the
debug assertion failure when buf_dump_thread is active. Both these
threads are created also in innodb_read_only mode. Depending on how
fast these threads react to the shutdown signal, the debug assertion
could be triggered.
There is no impact on non-debug servers, and very little impact on
debug servers either, because in innodb_read_only shutdown, no InnoDB
files will need to be written.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions