Marko Mäkelä 0288fa619f Do allow writes for innodb_force_recovery=2 or 3 ... While the primary purpose of innodb_force_recovery is to allow data to be rescued from an InnoDB instance that would crash due to some data corruption, the settings 1, 2, or 3 are relatively safe to use and there is no need to prevent write transactions in these modes. The setting innodb_force_recovery=4 and above can cause database corruption. For those modes, we already set the flag high_level_read_only to disable modifications, except DROP TABLE. MODIFICATIONS_NOT_ALLOWED_MSG_FORCE_RECOVERY: Remove. There is no need to spam the error log for each refused DML operation. It suffices to return an error to the client. There will be messages at startup if innodb_read_only or innodb_force_recovery are preventing writes.		2017-06-23 09:54:31 +03:00
..
include	Merge 10.1 into 10.2	2017-05-22 09:46:51 +03:00
r	Do allow writes for innodb_force_recovery=2 or 3	2017-06-23 09:54:31 +03:00
t	Do allow writes for innodb_force_recovery=2 or 3	2017-06-23 09:54:31 +03:00
disabled.def	Disable the innodb_defragment tests until MDEV-11336 is done	2017-05-08 22:06:32 +03:00