-
pg_easy_replicate
Easily setup logical replication and switchover to new database with minimal downtime
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
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
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
Related posts
-
Minimal downtime major PostgreSQL version upgrades with pg_easy_replicate
-
Minimal downtime major PostgreSQL version upgrades with pg_easy_replicate
-
Minimal downtime major PostgreSQL version upgrades with pg_easy_replicate
-
Minimal downtime major PostgreSQL version upgrades with pg_easy_replicate
-
Minimal downtime major PostgreSQL version upgrades with pg_easy_replicate