Isnt that only relevant to users that started with a very old setup guide?
I started in the still-beta stage (I’d say 20-30 updates before the 1.0.0 release) and already had the immich version of the postgre vector container in the compose template.
Comment on Immich v3.0.0 is out, with Workflows preview
Pika@sh.itjust.works 1 day ago
As an FYI to people who are upgrading and use a preexisting postgres database If you still use pgvectors.rs (if the command \dx on the immich database responds with vectors not vector) you will need to install both pgvector and vectorchord in order to continue using immich. This will require restarting your postgres instance at least once if not twice.
It threw me for a loop at first because of the similar naming. Just thought I would share.
Appoxo@lemmy.dbzer0.com 1 day ago Pika@sh.itjust.works 22 hours ago
I’m not sure, I was running 2.7.5 myself but i am not sure what version of immich I started with. I don’t think this would effect fully docker setups anyway, this would mostly effect people who had configured with a preexisting database. I think the docker edition with postgres built in upgraded for you awhile back unless you supplied an environment variable telling it to do otherwise.
Osiris@lemmy.world 1 day ago
Make sure you take a backup. Changing the docker container nuked my db. Had to restore from a backup
As usual during upgrades where loosing data is not acceptable.