Skip to content
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

Update to Zammad 6.4, and perform major dependency updates including postgres 17. #437

Merged
merged 1 commit into from
Nov 6, 2024

Conversation

mgruner
Copy link
Collaborator

@mgruner mgruner commented Nov 6, 2024

This includes a major update for the postgres dependency from 15 to 17, which requires manual action to upgrade the postgresql cluster data to the new version.

@mgruner mgruner requested review from monotek and t-shehab November 6, 2024 09:01
@mgruner mgruner added the feature label Nov 6, 2024
Copy link
Member

@monotek monotek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i guess link to upgrading docs will be added in the relase notes?

@mgruner
Copy link
Collaborator Author

mgruner commented Nov 6, 2024

Yes: https://www.postgresql.org/docs/17/upgrading.html, I will add it to the tag description.

@mgruner mgruner merged commit 004a96c into master Nov 6, 2024
4 checks passed
@mgruner mgruner deleted the update-64-dependencies branch November 6, 2024 09:57
@waja
Copy link
Contributor

waja commented Nov 7, 2024

Maybe pointing to https://github.com/tianon/docker-postgres-upgrade for upgrading a persisting docker volume might be useful.

@mgruner
Copy link
Collaborator Author

mgruner commented Nov 8, 2024

@terdinatore
Copy link

terdinatore commented Nov 10, 2024

@mgruner IMPORTANT: Using the docker method suggested by @waja breaks/prevents the database from starting because it's using the 17:bookworm image to upgrade instead of 17:alpine that is used in zammad-compose!

I got an error: database "zammad_production" has no actual collation version, but a version was recorded that could only be fixed by moving to 17:bookworm image in the zammad compose file. (See this: https://stackoverflow.com/a/78572273)

@tgoti
Copy link

tgoti commented Nov 13, 2024

Just as an idea, maybe this is a way easier solution to do the upgrade. Since I was searching for an easy way.
https://github.com/pgautoupgrade/docker-pgautoupgrade
It means to just change the image for the upgrade and switch it back afterwards. Maybe with the environment PGAUTO_ONESHOT: yes

@hubertnubert
Copy link

Just as an idea, maybe this is a way easier solution to do the upgrade. Since I was searching for an easy way. https://github.com/pgautoupgrade/docker-pgautoupgrade It means to just change the image for the upgrade and switch it back afterwards. Maybe with the environment PGAUTO_ONESHOT: yes

This is really the easiest solution.
Just stop the stack and enter (change the variables and your path to the db):

docker run --name pgauto -it \ --mount type=bind,source=/var/lib/docker/volumes/zammad_postgresql-data/_data,target=/var/lib/postgresql/data \ -e POSTGRES_DB=zammad_production \ -e POSTGRES_USER=zammad \ -e POSTGRES_PASSWORD=zammad \ -e PGAUTO_ONESHOT=yes \ pgautoupgrade/pgautoupgrade:17-alpine

Start the stack.
Finished.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants