Gordan Bobic via discuss <[email protected]> writes: > The problem is that unless you are running with: > - innodb_flush_log_at_trx_commit=1 > - sync_binlog = 1 (if binlog is enabled) > - sync_master_info = 1 (if slave) > > writes can be out of order which causes a problem.
It should be enough to run with innodb_flush_log_at_trx_commit=2 and sync_binlog=0 to have consistent snapshots. In this case, the data is written to the filesystem/OS (write(2) system call), but the fsync() is skipped. And this gives most of the performance benefit. But if innodb_flush_log_at_trx_commit=0, then the write is skipped, and snapshots will not be consistent. - Kristian. _______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
