-
-
Notifications
You must be signed in to change notification settings - Fork 233
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
⚠️ [Immich] Breaking change next release #1138
Comments
Thanks very much! |
I don't think postgres supports automatic database updates, so would this means I would need to create an addon for the postgres vector image, and users would have to recreate their databases using the new vector database addon ? |
no migration is needed just have to swap out the container for |
Great thanks! |
Hi, |
I would assume so, every instance would break unless the postgres container is changed to vector.rs |
Hi, indeed I just didn't found time to make the test environment to upgrade the postgres container, see if custom scripts need to be updated and check the impact on other addons depending on it. So for the moment I've paused the updates to be sure that nothing breaks for current users |
I've updated the postgres image, if there is no reported issues the immich image will be updated next saturday thanks VERY MUCH for that advance notice that ensured to do things in a progressive and hopefully non disruptive manner! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Thought I would give you a heads up that once imagegenius/docker-immich#248 is merged, instances will stop working, people will need to update their postgres image to pgvector
The text was updated successfully, but these errors were encountered: