Get the latest tech news
We migrated from AWS to GCP with minimal downtime
Lessons learned from moving terabytes of real time data between cloud providers.
A dangling replication slot left unattended for days would accumulate terabytes of write-ahead log and eventually run our filesystem out of space and shut down the database. Once the ZFS snapshot finally made it from the West Coast to the Midwest, we configured Postgres streaming replication, which went as you would expect, and we had a live hot standby in GCP, ready to go. We picked the lowest traffic period, midnight Pacific time, paused our PgCat pooler, waited for all remaining transactions to replicate, and shut down our AWS primary.
Or read this on Hacker News