# Future of "Legacy Postgres"? **URL:** \ **Category:** Questions / Help\ **Tags:** postgres, login-only\ **Created:** [April 16, 2025, 10:42pm UTC](https://community.fly.io/t/future-of-legacy-postgres/24609 "2025-04-16T22:42:31Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![pikdum](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/pikdum/32/16918_2.png) [@pikdum](https://community.fly.io/u/pikdum)\ **Post date:** [April 16, 2025, 10:42pm UTC](https://community.fly.io/t/future-of-legacy-postgres/24609/1 "2025-04-16T22:42:31Z")
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? ---
**Author:** ![halfer](https://avatars.discourse-cdn.com/v4/letter/h/df705f/32.png) [@halfer](https://community.fly.io/u/halfer)\ **Post date:** [April 17, 2025, 9:31pm UTC](https://community.fly.io/t/future-of-legacy-postgres/24609/2 "2025-04-17T21:31:55Z")
How are you using Postgres? Where are you seeing the legacy label? ---
**Author:** ![lillian](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/lillian/32/49616_2.png) [@lillian](https://community.fly.io/u/lillian)\ **Post date:** [April 17, 2025, 10:27pm UTC](https://community.fly.io/t/future-of-legacy-postgres/24609/3 "2025-04-17T22:27:10Z")
it’s labeled as legacy on the dashboard: ![sc_1744926279](https://global.discourse-cdn.com/fly1/original/3X/c/a/cab2631ffac994284de3c1010a0b74fcee700f34.png) 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. postgres-flex is open source on github, so it will still be possible to deploy/maintain it after we stop supporting it - or update to the latest minor version now, if you need. [GitHub - fly-apps/postgres-flex: Postgres HA setup using repmgr](https://github.com/fly-apps/postgres-flex) ---
**Author:** ![mayailurus](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/mayailurus/32/17593_2.png) [@mayailurus](https://community.fly.io/u/mayailurus)\ **Post date:** [April 17, 2025, 10:48pm UTC](https://community.fly.io/t/future-of-legacy-postgres/24609/4 "2025-04-17T22:48:04Z")
> [@lillian](#): > > 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): [https://community.fly.io/t/future-of-legacy-postgres/24185](https://community.fly.io/t/future-of-legacy-postgres/24185) [https://community.fly.io/t/fly-mpg-fully-managed-vs-postgres-flex-automatic/23707](https://community.fly.io/t/fly-mpg-fully-managed-vs-postgres-flex-automatic/23707) ---
**Author:** ![pikdum](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/pikdum/32/16918_2.png) [@pikdum](https://community.fly.io/u/pikdum)\ **Post date:** [April 17, 2025, 11:37pm UTC](https://community.fly.io/t/future-of-legacy-postgres/24609/5 "2025-04-17T23:37:25Z")
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](https://fly.io/docs/postgres/) ---
**Author:** ![lillian](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/lillian/32/49616_2.png) [@lillian](https://community.fly.io/u/lillian)\ **Post date:** [April 18, 2025, 12:02am UTC](https://community.fly.io/t/future-of-legacy-postgres/24609/6 "2025-04-18T00:02:00Z")
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. ---
**Author:** ![bcomnes](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/bcomnes/32/2563_2.png) [@bcomnes](https://community.fly.io/u/bcomnes)\ **Post date:** [April 18, 2025, 1:39am UTC](https://community.fly.io/t/future-of-legacy-postgres/24609/7 "2025-04-18T01:39:38Z")
Looking forward to a migration path off legacy automatic postgres to fly managed pg. Looking forward to see how fly does this! ---
**Author:** ![system](https://global.discourse-cdn.com/fly1/original/3X/6/e/6e8955d00cb218e186ebbe3a6ab06fefdce15290.svg) [@system](https://community.fly.io/u/system)\ **Post date:** [April 25, 2025, 1:39am UTC](https://community.fly.io/t/future-of-legacy-postgres/24609/8 "2025-04-25T01:39:49Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.