Moving a 4 TB Postgres database without downtime

Logical replication, a 90 second switch window and the three extensions that almost stopped us.

This is sample article text for the template. Replace it with your own post in the CMS: every paragraph, heading and list here is a normal rich text field.

What we measured

We pulled a year of invoices, split every line into compute, storage and traffic, and compared each account against its first full month on Aldridge.

• Compute cost fell by a median of 22%

• Storage cost was roughly flat

• Traffic cost went to zero because egress is included

What we would do again

Keep the old stack running for a week, move one service at a time, and switch DNS last. Most of the risk in a migration is in doing everything at once.