pg_easy_replicate
spock
| pg_easy_replicate | spock | |
|---|---|---|
| 11 | 3 | |
| 834 | 134 | |
| - | 7.5% | |
| 8.7 | 8.8 | |
| 2 days ago | 21 days ago | |
| Ruby | C | |
| MIT License | GNU General Public License v3.0 or later |
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.
pg_easy_replicate
-
Zero Downtime Postgres Upgrades
This is great! I wrote a tool that automates most of the things you came across. If you find it useful or would like to extend it with your feedback/ideas, I'd love to have them! Thanks for sharing
https://github.com/shayonj/pg_easy_replicate
- Minimal downtime major PostgreSQL version upgrades with pg_easy_replicate
-
Zero downtime major PostgreSQL upgrades with pg_easy_replicate
These are great shouts! Thank you so much for sharing. One of the operations I ran with this was ~500GB and yeah it takes a few hours to catchup. For us, it wasn't an issue, especially also since we were on AWS Aurora. However, that said, I can totally see it being not feasible on other database engine/systems. I considered the idea of dropping all the indices and re-creating it once the catch up is complete. I'd like pg_easy_replicate it to support that. It should make the initial COPY lot more swift. On a 200GB large DB it cut down down the total time by 90%.
Re: bi-directional replication, you read my mind :). https://github.com/shayonj/pg_easy_replicate/blob/8df94aa93f...
These two features are top of my list to support in pg_easy_replicate
- Show HN: Minimal downtime PostgreSQL upgrades with pg_easy_replicate
- Minimal Downtime Postgres Upgrades with Pg_easy_replicate
spock
-
Zero downtime major PostgreSQL upgrades with pg_easy_replicate
Cool, that's good info. Hadn't come across it before. :)
The GitHub repo page for it is here, for anyone else interested in taking a look: https://github.com/pgEdge/spock
-
How does database sharding work?
Spock may be of interest to you: https://pgedge.github.io/spock/
-
Show HN: Multi-Active Postgres at the Edge
Another week, another cutesy license: https://github.com/pgEdge/spock/blob/v3.0.19/PGEDGE-COMMUNIT...
What are some alternatives?
SearchCop - Search engine like fulltext query support for ActiveRecord
pg_party - ActiveRecord PostgreSQL Partitioning
flipper - 🐬 Beautiful, performant feature flags for Ruby.
jsonb_accessor - Adds typed jsonb backed fields to your ActiveRecord models.
Scenic - Versioned database views for Rails
with_advisory_lock - Advisory locking for ActiveRecord
chaosmonkey - Chaos Monkey is a resiliency tool that helps applications tolerate random instance failures.