Shlomi Noach bbd19abc9a - requiring --cut-over argument to be two-step|voluntary-lock (will add udf-wait once it is ready) ... The idea is that the user is forced to specify the cut-over type they wish to use, given that each type has some drawbacks. - More data in status hint - `select count(*)` is deferred till after we validate migration is valid. Also, it is skipped on `--noop`		2016-06-06 12:33:05 +02:00
..
base	- requiring --cut-over argument to be two-step|voluntary-lock (will add udf-wait once it is ready)	2016-06-06 12:33:05 +02:00
binlog	after timeout: reconnecting as new replica; skipping queries correctly	2016-05-23 11:12:59 +02:00
cmd/gh-ost	- requiring --cut-over argument to be two-step|voluntary-lock (will add udf-wait once it is ready)	2016-06-06 12:33:05 +02:00
logic	- requiring --cut-over argument to be two-step|voluntary-lock (will add udf-wait once it is ready)	2016-06-06 12:33:05 +02:00
mysql	- Handling gomysql.replication connection timeouts: reconnecting on last known position	2016-05-19 15:11:36 +02:00
os	renaming to gh-ost	2016-05-16 11:09:17 +02:00
sql	Fixing single-row table migration	2016-05-18 14:53:09 +02:00