We’re on unmanaged / “legacy” PG and would like to migrate to MPG but can’t because of lack of multi-schema support. So as of now we find ourselves operating our business on a “deprecated” service. Doesn’t feel great! Would love some reassurance that “unmanaged” PG will continue to be supported until MPG has feature parity. Would also be great to get a timeline for multi-schema support.
3 Likes
I realise the benefits of an in-cloud platform, but if you’re not keen on continuing with deprecated things, you can always swap to an external managed service. I am trying Supabase presently, and it seems pretty good.
1 Like
Thanks but we do want a fly-managed service. Hoping to get a response from someone from fly.
I work at fly but unfortunately I don’t have the answer you’re looking for.
Legacy/Unmanaged Postgres isn’t a service provided or managed by us. We created some scripts to set up and manage databases yourself; these are open source and you are free to fork the repo to make any changes you need.
Once the fly pg commands are removed from flyctl, we will add equivalent scripts and/or documentation to the open source repo for people to continue using or work off of (the details haven’t been decided yet, it will be some time).
As for Managed Postgres: being a managed service, there are tradeoffs we as a service provider have to make - the features we can support for a wide customer base are necessarily limited compared to the same service administered by a user themselves. We are starting to grow the MPG team so we can add more requested features, but some use cases are just better suited for a self-managed app.
To reply to your question directly, super-user actions such as creating new schemas are planned, however I can’t give you a timeline for them; we are mainly working on stability at the moment.
2 Likes
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.