Supabase is deprecating Fly’s Postgres offering managed by Supabase on April 11, 2025.
Why are we deprecating this offering?
This deprecation enables us to focus on a new architecture for scale-to-zero databases, zero-downtime upgrades (more on this later), and more. Afterward, we’ll re-evaluate multi-cloud deployments beyond AWS, our current cloud provider.
What’s the current status of Fly Postgres on Supabase?
We have disabled Fly Postgres signups and existing Fly Postgres customers will no longer be able to spin up new projects on Supabase. However, you can still access any existing Fly Postgres database.
What is the deprecation timeline?
Before April 11:
You will still be able to access your existing Fly Postgres projects. We strongly recommend that you transition to Supabase’s or Fly’s native Postgres offering as soon as possible.
On April 11:
Your Fly Postgres projects are removed from our platform.
Reach out to our support if you have any questions or concerns regarding this deprecation.
I'm confused reading the migration documentation -- the "Fly Postgres" is already on Supabase? So how can I migrate it from Supabase to Supabase?
2 replies
In plainer terms for future readers; it appears the advice for "I login to Supabase through a Fly Dashboard" is that even though both databases are on Supabase:
Prerequisites: Two hiccups: First, the direct connection URL suggested I couldn't use it because of IPv6 limitations where I was connecting from, so I needed to use the Transaction Pooler URL rather than the Direct Connection URL. Second, it was necessary to make sure I had Postgresql@15 installed so that my computer and the external matched, since I had 14 locally and what I was talking to wanted 15.
After that, the instructions will look similar to what's in the documented link:
pg_dump "[connection pool URL here]" \
--clean \
--if-exists \
--quote-all-identifiers \
--no-owner \
--no-privileges \
> dump.sql
Create an account on Supabase separate from your Fly account, since it appears those are what are going away in March 2025. Get the transaction pooler URL from that account and run:
psql -d "[new connection URL here]" -f dump.sql
Is this expected? We have restarting project a couple of times but it's still down. P0 for us, unable to establish connection with DB.
0 replies