22 ms·
These pitfalls are one reasons why I built Reshape [0], which aims to automate zero-downtime schema migrations. I can’t say it avoids all of them but we are wo
by fabianlindfors 2y ago
These pitfalls are one reasons why I built Reshape [0], which aims to automate zero-downtime schema migrations.
I can’t say it avoids all of them but we are working on a new product that would. If you are interested in this space (and Postgres specifically), I’d love to hear from you: fabian@reshapedb.com
[0] https://github.com/fabianlindfors/reshape https://github.com/fabianlindfors/reshape
- smw 2y agoAny chance that works for crdb?
- fabianlindfors 2y agoUnfortunately not as Cockroach doesn't support triggers, which is what powers Reshape. We are looking into how to widen support though for our next product, reach out to fabian@reshapedb.com if you'd be interested in something like that!
- andyzweb 2y agoit might work but keep in mind schema changes in cockroachdb very different under the hood. for one they are not transactional and run in the background https://www.cockroachlabs.com/docs/stable/online-schema-changes#limitations https://www.cockroachlabs.com/docs/stable/online-schema-chan...
- fabianlindfors 2y agoSee my other comment. Unfortunately Cockroach doesn't do much in terms of helping with zero-downtime schema migrations :/