The near-term focus of SchemaBot is to support the majority of Block's internal use-cases, which happens to be mostly MySQL and some Vitess apps. However, we also do run some Postgres databases, and our plan is to extend SchemaBot to support Postgres after MySQL + Vitess is fully rolled out. This entails building a new Postgres engine, ideally using existing Postgres schema change tooling, but we're willing to build out support for features that don't yet exist (e.g. see https://github.com/block/spirit for our gold standard of what we'd like to do with schema change tooling)
The near-term focus of SchemaBot is to support the majority of Block's internal use-cases, which happens to be mostly MySQL and some Vitess apps. However, we also do run some Postgres databases, and our plan is to extend SchemaBot to support Postgres after MySQL + Vitess is fully rolled out. This entails building a new Postgres engine, ideally using existing Postgres schema change tooling, but we're willing to build out support for features that don't yet exist (e.g. see https://github.com/block/spirit for our gold standard of what we'd like to do with schema change tooling)