Postgres 16 --> 17 Documentation
Hi folks. Home user here who's slowly learning how to self-host things over the past couple of months. I went to update my Zitadel docker container today, and noticed that on the lastest compose.yaml deployment example, we now use postgres 17. My existing setup uses postgres 16 from when I first created the container back in March of this year.
Is there any documentation on how to migrate from v16 to v17? I've looked through release notes, this server, github issues etc - but can only find issues relating to the old cockroach migration.
3 Replies
Postgres 16 -> 17 upgrade is not necessarily a Zitadel related topic. You can find some instructions for a secure upgrade on Postgres websites.
In a perfect world , you could simply replace the Postgres container:
However, that might or might not work well. So if you're planning on doing that, you should definitely have a backup.
oxyconit describes a method that is suitable for smaller databases and is definitely a more secure procedure: How to upgrade PostgreSQL from 16 to 17 in Docker
Oxycon Blog
How to upgrade PostgreSQL from 16 to 17 in Docker
Keeping your PostgreSQL database up-to-date is crucial for security, performance, and access to new features. This guide walks through upgrading PostgreSQL from version 16 to 17 in a Docker environment.
Step 1: Prepare your environment
First, update your docker-compose.yml file to include both PostgreSQL versions. (please also make sure
Thank you, I will look into this. I did try simply changing the image, but it refused to initialise as it recognised the DB was made with an older version. To be honest - Zitadel v3.30 is working fine with Postgres 16, so unless it breaks - I shall likely stick with 16.
I can verify with the team again but ATM
Currently versions >= 14 are supported. is our approach