Marko Mäkelä f458b40f66 MDEV-22827 InnoDB: Failing assertion: purge_sys->n_stop == 0 ... When MDEV-22769 introduced srv_shutdown_state=SRV_SHUTDOWN_INITIATED in commit efc70da5fd we forgot to adjust a few checks for SRV_SHUTDOWN_NONE. In the initial shutdown step, we are waiting for the background DROP TABLE queue to be processed or discarded. At that time, some background tasks (such as buffer pool resizing or dumping or encryption key rotation) may be terminated, but others must remain running normally. srv_purge_coordinator_suspend(), srv_purge_coordinator_thread(), srv_start_wait_for_purge_to_start(): Treat SRV_SHUTDOWN_NONE and SRV_SHUTDOWN_INITIATED equally.		2020-06-08 10:35:06 +03:00
..
srv0conc.cc	MDEV-22721 Remove bloat caused by InnoDB logger class	2020-06-04 10:24:10 +03:00
srv0mon.cc	Merge 10.1 into 10.2	2019-05-13 17:54:04 +03:00
srv0srv.cc	MDEV-22827 InnoDB: Failing assertion: purge_sys->n_stop == 0	2020-06-08 10:35:06 +03:00
srv0start.cc	MDEV-22827 InnoDB: Failing assertion: purge_sys->n_stop == 0	2020-06-08 10:35:06 +03:00