Was planning to deploy a new application on Fly, but noticed that the postgres databases are now labeled as “Legacy Postgres”.
Will this not be maintained after shipping “Managed Postgres”?
Noticed it’s behind by a few minor versions now and it took ~5 months to support Postgres 17, so is it even actively maintained now?
there will probably be a more “official” communication on what this will look like, but: yes, we are going to deprecate the current unmanaged “automated postgres” templates for the new Managed Postgres offering.
Thanks for the clarifications… I’ll use this space to just append a couple quick references to older, now-closed threads, , so the forum software will automatically create back-links (from those to this answer):
Bummer. Will it still be possible to deploy/maintain using flyctl postgres commands, or do you recommend switching to a regular app for database deploys?
I was thinking of forking, but the documentation made it seem like it wasn’t the ideal approach:
One caveat is that once you fork, you won’t be able to use fly postgres commands to administer your app. Fly Postgres · Fly Docs
yes, fly postgres commands will be going away, or being repurposed for managed postgres, I’m not sure yet.
I’m not personally familiar with the flyctl postgres implementation, but I assume if there’s any logic that’s only inside flyctl it’ll be moved or replicated elsewhere.