[joelrwilliams1]

What was most shocking to me was that it took a week to migrate 40GB.

I once migrated 1TB from RDS Oracle to RDS Aurora MySQL in 6 hours. I'm not familiar with Supabase, maybe there's a lot more to the data migration process?

[burggraf]

Supabase developer here. It shouldn't (and doesn't) take a week to migrate 40GB, I'm sure most of that time was strategizing, analyzing, and testing things. Supabase is pure Postgres running on AWS, so migrations are pretty straightforward. Things mostly depend on where you're migrating to/from, and the network latency between the source and destination. 40GB should take minutes in most cases.

[stevekrouse]

There were a couple of factors why it took a week:

1. We wanted to avoid downtime, so the pg dump was slowed down because it was happening alongside production use of the db

2. We abuse postgres in a couple of ways (too many large json columns) which makes it harder to export and import

3. We were moving between cloud regions and cloud providers.

4. I'm a bit of a database ops noob (part of why supabase was appealing in the first place) so I had to learn how to do all these things. Like burggraf said, a lot of that week was planning, trial and error, test runs, mistakes that would cost full days, etc.