-
Notifications
You must be signed in to change notification settings - Fork 22
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.
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
image pgautoupgrade/pgautoupgrade:15-alpine upgrades database to postgres 16 #28
Comments
Oh crap. Yeah, 15-alpine is supposed to upgrade stuff to 15, and not past that. Definitely a bug. We greatly changed the build process for images over the last 2 days in order to enable ARM64. Looks like it's not quite right. @andyundso Are you ok to look into this? |
very sorry about that, was a mistake by me in the pipeline configuration. fixed with #29. |
Thanks @andyundso. 😄 Super sorry about that @mx-bernhard. 😦 |
fixed images are now available on Docker Hub.
Really sorry about this mistake, I should have checked the Docker layers on Docker Hub and I would have seen the issue beforehand. |
Nothing bad happened for me, I have backups, as one should. Also, I had time to investigate today. 👍 for fixing so fast. |
I thought that
pgautoupgrade/pgautoupgrade:15-alpine
was just ensuring that after the upgrade the database version was 15 and not 16 andpgautoupgrade/pgautoupgrade:16-alpine
was doing the same but with database version 16 as a target. If I changePGTARGET
environment variable to 15 before starting the container with imagepgautoupgrade/pgautoupgrade:15-alpine
, no upgrade is started. This is either a bug or a missing in the documentation (to me, it looks like the former). Startingpgautoupgrade/pgautoupgrade:15-alpine
like this yields 16 and not 15:The text was updated successfully, but these errors were encountered: