Replies: 3 comments
-
Quick update, --skip-backup option allow me to finalize the setup and get a working instance. Not an ideal but working condition. It seams that the issue is limited to a pg_dump command only and it doesn't impact the db update. Not sure if the automatic backup (GUI option) is impacted too. Thanks |
Beta Was this translation helpful? Give feedback.
-
@icvdok yes the issue is that the docker image ships with postgres-13-cli which is not compatible with your postres-17 server I have just started an issue here to try and address this: #9040 For now you will have to skip the backup option (sorry)
Yes it will be, it runs using the same CLI tool |
Beta Was this translation helpful? Give feedback.
-
Many thanks for the answer and clarification, I've my own backup system for the central DB server but I'll keep for the moment the DB on a dedicated instance. Would be good to have the issue solved but it's not a big problem. Just for your info, I did some checks on my tst env and, except for the backup issue, the inventree is (so far) running fine on latest PG version. |
Beta Was this translation helpful? Give feedback.
-
Hello, I would like to test Inventree (clean install) connected to my "central" postgresql server.
My .env file contain the required db connection information. I've created an empty db on my server (tstinventree) and a related user to connect.
The invoke update command report a db version mismatch:
There are specific Postgresql version requirements or i can do something to move forward with the setup?
Thanks for the support.
Beta Was this translation helpful? Give feedback.
All reactions