# fly migrate-to-v2 - postgres edition **URL:** \ **Category:** Fresh Produce\ **Created:** [April 10, 2023, 5:35pm UTC](https://community.fly.io/t/fly-migrate-to-v2-postgres-edition/12140 "2023-04-10T17:35:20Z")\ **Posts on this page:** 1\ **Showing post:** 37
**Author:** ![danwetherald](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/danwetherald/32/37600_2.png) [@danwetherald](https://community.fly.io/u/danwetherald)\ **Post date:** [May 4, 2023, 10:54pm UTC](https://community.fly.io/t/fly-migrate-to-v2-postgres-edition/12140/37 "2023-05-04T22:54:09Z")
@shaun nope, nothing has changed, haven’t been directed to try anything new. Everything is still the same on my end. > [@Old fly postgres app running V1 can not be migrated and is stuck in bad state - restart not available - migrate not available](https://community.fly.io/t/old-fly-postgres-app-running-v1-can-not-be-migrated-and-is-stuck-in-bad-state-restart-not-available-migrate-not-available/12702): > > We have a few old fly pg deployments on v1 and we are completely stuck, we are not able to restart these or migrate them to v2. We cant seem to find a way to get that second VM to properly restart and begin to pass all its checks. Error: cmd/keeper.go:720 cannot get configured pg parameters {"error": "dial unix /tmp/.s.PGSQL.5433: connect: no such file or directory"} ERROR cmd/keeper.go:1452 different local dbUID but init mode is none, this shouldn't happen. Something bad happened … --- _[View the full topic](https://community.fly.io/t/fly-migrate-to-v2-postgres-edition/12140)._