Kristian Nielsen 36e81a23c5 MDEV-11937: InnoDB flushes redo log too often ... Problem was introduced with the InnoDB 5.7 merge, the code related to avoiding extra fsync at the end of commit when binlog is enabled. The MariaDB method for this was removed, but the replacement MySQL method based on thd_get_durability_property() is not functional in MariaDB. This commit reverts the offending parts of the merge and adds a test case, to fix the problem for InnoDB. But other storage engines are likely to have a similar problem.		2017-08-07 18:23:55 +02:00
..
trx0i_s.cc	Remove trx_t::has_search_latch and simplify debug code	2017-06-16 13:17:05 +03:00
trx0purge.cc	Do allow writes for innodb_force_recovery=2 or 3	2017-06-23 09:54:31 +03:00
trx0rec.cc	Assert that DB_TRX_ID must be set on delete-marked records	2017-07-01 11:02:58 +03:00
trx0roll.cc	Merge 10.1 into 10.2	2017-05-23 11:09:47 +03:00
trx0rseg.cc	Merge 10.1 into 10.2	2017-06-08 12:45:08 +03:00
trx0sys.cc	Simplify access to the binlog offset in InnoDB	2017-06-29 23:03:39 +03:00
trx0trx.cc	MDEV-11937: InnoDB flushes redo log too often	2017-08-07 18:23:55 +02:00
trx0undo.cc	MDEV-12289 Keep 128 persistent rollback segments for compatibility and performance	2017-03-31 18:53:04 +03:00