Go to file

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

.github

initial CONTRIBUTING.md

2016-05-20 13:10:50 +02:00

doc

fix typos

2016-05-27 16:03:47 -07:00

- 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

vendor

added vendor packages

2016-04-01 16:04:27 +02:00

build.sh

- 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

LICENSE

Initial commit

2016-03-21 11:08:52 +01:00

README.md

adding documentation

2016-05-25 12:34:37 +02:00

README.md

gh-ost

GitHub's online schema migration for MySQL

gh-ost allows for online schema migrations in MySQL which are:

Triggerless
Testable
Pausable
Operations-friendly

How?

WORK IN PROGRESS

Please meanwhile refer to the docs for more information.

What's in a name?

Originally this was named gh-osc: GitHub Online Schema Change, in the likes of Facebook online schema change and pt-online-schema-change.

But then a rare genetic mutation happened, and the s transformed into t. And that sent us down the path of trying to figure out a new acronym. Right now, gh-ost (pronounce: Ghost), stands for:

GitHub Online Schema Translator/Transformer/Transfigurator

Authors

gh-ost is designed, authored, reviewed and tested by the database infrastructure team at GitHub: