News for hackers. Stuff that matters.
Re:My Notes on Gitlab's Postgres Schema Design (2022) by semiquaver on Monday February 19, 2024 @11:52AM (#39431920)
What has worked in my experience:

- decouple migration execution from code deployment. Require that all migrations are in totally separate PRs can be run well-in-advance of the code that depends on the db change being run

- maintain a stateful migration execution system using an online schema change system supervised by DBAs

- PRs adding migrations still need to be merged and deployed, but can only do so after the actual migration has run.

Re:My Notes on Gitlab's Postgres Schema Design (2022) by tianzhou on Tuesday February 20, 2024 @09:52AM (#39441983)
+1. We have been working on a schema migration tool called Bytebase for 3+ years. And we follow the similar principles.