Skip to content

fix unmanaged psql image update explanation #2378

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kubosuke wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix unmanaged psql image update explanation #2378

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion postgres/managing/upgrades.html.markerb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ And upgrade with:
fly image update -a <postgres-app-name>
```

The update only works if the major Postgres version in your existing Postgres app matches that in the newest Postgres app release, for example `postgres-flex:15.2` to `postgres-flex:15.3`.
By default, `fly image update` does not change your image tag. It resolves the same repository and tag your Machines already use (for example `flyio/postgres-flex:15.2`) and updates them to the latest image Fly publishes for that ref—usually a newer digest or build on that tag. To use a different tag (for example moving from `:15.2` to `:15.3`), set the image explicitly with [`fly image update --image`](/docs/flyctl/image-update/).

Upgrading Postgres across major versions is more complicated, and right now the way to do this is to provision a new cluster and restore a backup of your database data into it.

Expand Down