go-pg-migrate
pgroll
go-pg-migrate | pgroll | |
---|---|---|
- | 14 | |
10 | 2,524 | |
- | 4.3% | |
2.9 | 9.4 | |
7 months ago | 5 days ago | |
Go | Go | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
go-pg-migrate
We haven't tracked posts mentioning go-pg-migrate yet.
Tracking mentions began in Dec 2020.
pgroll
-
Building a Managed Postgres Service in Rust
I thought I recognized xataio - they submitted pgroll a few months back https://news.ycombinator.com/item?id=37752366 (https://github.com/xataio/pgroll - Apache 2)
- Revolutionizing PostgreSQL Schema Changes with pg-osc
- PostgreSQL zero-downtime and reversible migrations
-
How pgroll works under the hood
At the start of October we released pgroll, an open source tool for zero-downtime, reversible schema migrations for Postgres.
-
Introducing pgroll: zero-downtime, reversible, schema migrations for Postgres
If you have any suggestions or questions, please open an issue in our GitHub repo, reach out to us on Discord or follow us on X / Twitter. We'd love to hear from you and keep you up to date with the latest progress on pgroll.
-
Pgroll: zero-downtime, undoable, schema migrations for Postgres
Any pgroll operations[0] that require a change to an existing column, such as adding a constraint, will create a new copy of the column and backfill it using 'up' SQL defined in the migration and apply the change to that new column.
There are no operations that will modify the data of an existing column in-place, as this would violate the invariant that the old schema must remain usable alongside the new one.
[0] - https://github.com/xataio/pgroll/tree/main/docs#operations-r...
-
Database Migrations
This is a fantastic article! It shows that even simple migrations (like adding or removing a column) can be quite tricky to deploy in concert with the application deployement.
We (at Xata) have tried for a while to come up with a generic schema migration system for PostgreSQL that makes this easier. We ended up using views and temporary columns in such a way that we can provide both the "old" and the "new" schema simultaneously. Up/down triggers convert newly inserted data from old to new and the other way around. This also has the advantage the it can do rollbacks instantly by just dropping the "new" view.
We were just planning to announce this as an open source project this week, but actually it is already public, so if you are curious: https://github.com/xataio/pgroll
What are some alternatives?
cockroach - CockroachDB - the open source, cloud-native distributed SQL database.
migrate - Database migrations. CLI and Golang library.