gh-ost

Many additions since 1.0.21. The ultimate breakdown is https://github.com/github/gh-ost/compare/v1.0.21...v1.0.28

Notable:

• support for DATETIME subsecond resolution
• user-commanded throttling implies complete silence, not even heartbeat is written
• fixed log_slave_updates check on --test-on-replica and --migrate-on-replica
• cleanly closing streamer connection (connection that imposes as a replica) upon completion
• on --exact-rowcount, --concurrent-rowcount now defaults true
• added validation to confirm table structure on master & replica is identical (yes, the counter case happened)
• correct (though suboptimal) behavior on enum being part of the migration key

Many additions since 1.0.20. The ultimate breakdown is https://github.com/github/gh-ost/compare/v1.0.20...v1.0.21

Notable:

• support for --critical-load-interval-millis -- a 2nd threshold sample to allows for graceful recovery from sudden and immediate spike.
• better support for non-utf charsets; help requested.
• support for dropping foreign keys. Watch out! This will drop your foreign keys. That's what it does.
• Better support for tungsten. Read the story

Notable:

• Support for latin1 (but for other character sets, please see https://github.com/github/gh-ost/issues/228). utf8 and utf8md4 supported out of the box.
• named cut-over: a configurable protection mechanism to require table name when commanding postpone on interactive commands. --force-named-cut-over is introduced.

Other minor enhancements.

EXPERIMENTAL RELEASE

This includes https://github.com/github/gh-ost/pull/227, solving https://github.com/github/gh-ost/issues/226: non-UTF8 characters sets.

This particular release only addresses latin1, and if all goes well we can expand to all character sets.

Notable:

• Support hooks: external processes invoked by gh-ost at specific points in execution
• Sub-second lag resolution: if you require your replicas to lag within subsecond threshold, this is now supported
• RDS: this release should work with RDS, see discussion -- we will formalize documentation once behavior is tested more
• Tungsten: supply --tungsten --assume-master-host=the.master.com
• master-master improved support: explictly specify the master via --allow-master-master --assume-master-host=the.master.com. See cheatsheet
• Improved status report (ETA shows estimate even while throttling)

Notable:

• --concurrent-rowcount (https://github.com/github/gh-ost/issues/194): with --exact-rowcount, issue the count(*) concurrently even as row copy takes place (row count gets updated throughout the migration)
• Using STRICT_ALL_TABLES for all operations, as safety net ()
• Fixed support for 5.5 (https://github.com/github/gh-ost/issues/184)
• Relaxed config file parser (https://github.com/github/gh-ost/issues/198)

Notable:

• Last fixes to time-size related issue (gh-ost is now fully UTC)
• Fixed column rename DML apply failure

Notable:

• Fix to timezone issue https://github.com/github/gh-ost/issues/161

Notable:

• Fixed integrity issue https://github.com/github/gh-ost/issues/157 (unsigned int values)
• Remove SUPER requirement when running with RBR: https://github.com/github/gh-ost/pull/156, introducing --assume-rbr

Various PR merges and fixes:

• relaxed check for log_slave_updates (closes #135)
• bailing out when triggers exist (closes #141), but also note #153
• cleanup socket file
• ipv6 support in MySQL connection
• More user friendly error reporting for privileges
  and more.

Thank you kindly to all contributors!

Generally available

Generally available

This is the first GA release of gh-ost, now that it's being used in production.

Pre-production, use at your own risk

Pre-production, use at your own risk

Pre-release, use at your own risk

Pre production. Use at your own risk.

Pre production. Use at your own risk.

Pre-production! Use at your own risk.

Insofar, only tested on production servers via --test-on-replica