One of the more popular requests that the Managed Postgres team has received is Postgres 17 support. Heretofore (Kurt inspired me to use this word), only PG 16 was available—but starting today you can provision new MPG clusters on PG 17.
It’s faster, leaner on maintenance, and ships modern SQL/JSON features out of the box.
This hopefully comes as welcome news for folks who want to switch to MPG from an existing unmanaged Postgres DB running PG 17, or anyone migrating from another managed provider.
For now, you’ll need to provision the cluster via the Fly.io dashboard. The flyctl create and launch flows still default to PG 16.
What’s not there yet?
flyctlsupport (coming very soon)- Upgrading existing clusters
- Restoring a PG 16 backup to PG 17
If you want to migrate an existing cluster to a fresh PG 17 cluster, you’ll have the best luck with a stock-standard pg_dump/pg_restore routine.
What’s next
We’ll be tracking PG 17 provisions over the next couple of weeks and, if all goes well, we’ll make it the default version. Some time after that, we’ll remove the ability to provision PG 16 altogether.
If you hit a snag, drop a note below or open a ticket from the support portal.