Hello Kristian,
Thanks for the feedback.
For me, the biggest design goal is to have a way for slaves to be
crash safe without requiring the storage engine to fsync every
transaction it processes. This would be a huge performance win.
In a world where slave replication is single threaded, I solut
Thinking more about this, I cannot quite make up my mind of the best approach.
I would like to get some input.
On the one hand, when binlog is enabled on a slave, it really is the best
solution for storing replication state and crash safety.
On the other hand, running a slave with innodb_flush_lo
2 matches
Mail list logo
