You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pgml-cms/blog/how-we-migrated-from-aws-to-gcp-with-minimal-downtime.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -117,9 +117,9 @@ The database files were the same on GCP and AWS, if one checked them for their "
117
117
118
118
###The cutover
119
119
120
-
The final step was to move our customers' traffic from AWS to GCP, and do so without losing a byte of data. We picked the lowest traffic period, midnight Pacific time, and shut down our AWS primary.
120
+
The final step was to move our customers' traffic from AWS to GCP, and do so without losing a byte of data. We picked the lowest traffic period, midnight Pacific time,paused our[PgCat](/docs/product/pgcat/) pooler, waited for all remaining transactions to replicate,and shut down our AWS primary.
121
121
122
-
As soon as the Systemd service stopped, we changed the DNS record to point to our GCP standby and ran`SELECT pg_promote()`. Traffic moved over almost immediately, thanks to our low DNS TTL and we were back in business.
122
+
As soon as the Systemd service stopped, we changed the DNS record to point to our GCP standby and ran`SELECT pg_promote()`. Traffic moved over almost immediately, thanks to our low DNS TTL, and we were back in business.