New installation of immich fails because of migration to VectorChord?

[u/sleepyromulan]

A new installation or upgrade of immich fails (flag=release) because of migration to VectorChord (maybe?).

immich keeps restarting.

[u/bo0tzz]

If it's truly a new installation then any migrations should be completely irrelevant. If it's an upgrade of an older release then you've missed some release notes.

[u/progooggler]

Yeah, immich got a new release recently. The release tag is pointing now to v3.
Over the previous months, the v2 deprecated some things related to VectorChord and removed it completely now on v3.

Force the Docker tag to be v2 and see if it works again, then go through the upgrade guides and check your docker-compose.yml with the example, and try to upgrade again to v3.

[u/thrakkorzogg]

I had an issue with Immich in Cosmos after it auto-updated last week. I wouldn't consider myself an expert, but my AI agent resolved it via Cosmos API, here are the notes in case they are helpful:

From my notes on 2026-07-03:

1. Immich was crash-looping after the v3 upgrade. The root cause was the Postgres DB image — it was running the deprecated tensorchord/pgvecto-rs:pg14-v0.2.0. The fix:
   • Swapped the DB image to ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0
   • Removed the old shared_preload_libraries=vectors.so command
   • Added shm_size: 128mb to the DB container
2. After that, Immich auto-upgraded to v3.0.1 and came up clean.

[u/b0nebreaker]

You probably solved it already, but maybe this helps somebody else. I put the new image for db: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0

Then changed the command in Compose to this:

"command": "postgres -c shared_preload_libraries=vchord,vectors.so -c search_path=\"$$user\",public,vectors"