I actually did try that earlier when I saw your comment on this post. But it did not work either as the command got stuck on the health checks, so I ended up canceling it:
▲ fly image update -c fly.db.toml
? Update `urbanave-db` from flyio/postgres:14.2 v0.0.22 to flyio/postgres:14.4 v0.0.25? Yes
Release v13 created
You can detach the terminal anytime without stopping the update
==> Monitoring deployment
1 desired, 1 placed, 0 healthy, 0 unhealthy [health checks: 3 total, 1 passing, 2 critical]
^CFailed Instances
failed fetching alloc 9da7f547-7d75-e914-b20d-a093c8ec8985: context canceled%
But now I see that the image was still updated as the postgres version now shows 14.4 and rerunning the command shows:
▲ fly image update -c fly.db.toml
Error image is already running the latest image
Why would this happen now when the DB usually works without issues?
Can you clarify what you mean by “overloaded”? What can we do to avoid this and other DB issues?