Upgrade MAY break postgres container

[eduardogsilva]

Description:
This project was initially set up with postgres:latest in the Docker configuration. Recently, PostgreSQL updated from version 16 to 17, and this upgrade is not seamless. The data directory initialized by PostgreSQL 16 is not compatible with PostgreSQL 17, causing compatibility issues.

Temporary Solution:
As a temporary fix, I have pinned the PostgreSQL version to postgres:16 in the Docker setup. This will prevent unexpected upgrades from breaking the container.

For Users Already on PostgreSQL 17:
If your setup is already using PostgreSQL 17, you’ll need to edit the docker-compose.yml file to ensure the PostgreSQL version matches the data directory you’re using.

Feel free to reach out if you encounter any further issues related to this upgrade.

[eduardogsilva]

This is an old issue from 2014 docker-library/postgres#37

Other related issues:
docker-library/postgres#157
docker-library/postgres#1125

[eduardogsilva]

It is old, but still very relevant. I was just wondering why my app stopped working. It would be very convenient that the data migration would be done automatically. An approach similar to https://github.com/pgautoupgrade/docker-pgautoupgrade would be desirable so that we users don't have to worry about any updates :)

I believe that this docker-pgautoupgrade is mentioned as a possible solution for this issue on docker-postgres. This should be fixed on postgres project.

This is out of the scope of routerfleet project. I don't feel comfortable orienting people to manually migrate their databases. There is a huge potential for data loss. For this moment, I will just lock the project to postgres 16 instead of latest.

[Lukas-J]

@eduardogsilva That's right. Sorry, I mixed up repos when I commented on this issue. I did the same, and just fixed postgres version 16 to my compose file; so I will just have to worry about this issue again, when postgres 16 is at end of life.