pg-schema-diff

Hey, are you using some tool like the unmaintained migra https://github.com/djrobstep/migra (perhaps using this tool https://github.com/blainehansen/postgres_migrator) or pg-schema-diff https://github.com/stripe/pg-schema-diff or maybe this other unrelated pg-schema-diff https://github.com/zombodb/pg-schema-diff anything like it? Is it open source? I mean, I see you say > We then use a schema diff tool, like migra, to figure out the necessary updates to views and functions when generating the migration file. But "like migra" is very nonspecific. I guess you are not using migra itself

There are a few stand-alone declarative Postgres tools available, including Stripe's pg-schema-diff [1], Tusker [2] which wraps Migra [3], and sqldef [4] which supports multiple DBMS. For sake of completeness for users of other databases: for SQLite check out stb-tester's migrator [5], and last but not least for MySQL/MariaDB there's my tool Skeema [6]. [1] https://github.com/stripe/pg-schema-diff [2] https://github.com/bikeshedder/tusker [3] https://github.com/djrobstep/migra [4] https://github.com/sqldef/sqldef/ [5] https://david.rothlis.net/declarative-schema-migration-for-s... [6] https://github.com/skeema/skeema

> it doesn’t tell you the consequences of changing an attribute (database restart or other downtime-inducing stuff) Modern diff tools are designed to provide better guardrails in these situations. For eg, pg-schema-diff [0] tries to generate zero downtime migrations by using lock-free migrations and warns you about potentially hazardous migrations. I think it's good direction to bake these best practices into the tooling itself, rather than relying purely on the experiences of engineers. [0] https://github.com/stripe/pg-schema-diff