Postgres 13 upgrade #58
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
Currently the docker-compose and files support postgres13 only. Is there a plan to ensure compatibility with later versions.
Postgres13 goes EOL in November this year (2025).
https://www.postgresql.org/support/versioning/
Releases
I think you should be able to modify
postgres:13in thedocker-compose.ymltopostgres:17for a new database with no problems (and should be fully supported), but if you need to migrate an existing database, you'll need to update the database somehow (traditionally manually dumping and restoring the database).I need to do more research if there are any docker images that can help with this, I think https://github.com/pgautoupgrade/docker-pgautoupgrade may work automatically but I have yet to try it. However, from reading the readme it seems like if you just change
postgres:13topgautoupgrade/pgautoupgrade:17-alpine, it should update it for you automatically!I need to migrate my instances as well so I will definitely be doing this, thank you for the reminder!
Yo I just ran this on my instance and it worked like a charm!!! I'll add a line in the readme for db instructions, but I just changed
postgres:13topgautoupgrade/pgautoupgrade:17-alpine, did my regulardocker-compose up -d, and then changed it back topostgres:17withdocker-compose up -djust to avoid needing to recheck the database version on every boot.All the postgres updates that I know about are fully backwards compatible so there shouldn't be an issue updating the database ahead of my repo in the future as well. I hope this helps!
Thank you so much for this, this makes db updates so easy now I've been updating all the databases on my server, including this gitea one which should be much faster now as well, this is awesome!!