Error: The VectorChord extension version is 0.4.3, but Immich only supports >=0.3 <0.4

Hello, everyone! Ive started update Immich Server from 1.132.3 to 1.133.0 (applied breaking changes in Github https://github.com/immich-app/immich/discussions/18429) But, while updating, I see the next error in Immich Server: ``` Error: The VectorChord extension version is 0.4.3, but Immich only supports >=0.3 <0.4. ``` 1) First of all, I checked the "pg_extensions" in PSQL Server: ``` postgres=# SELECT * FROM pg_extension; oid | extname | extowner | extnamespace | extrelocatable | extversion | extconfig | extcondition --------+---------+----------+--------------+----------------+------------+-----------+-------------- 13766 | plpgsql | 10 | 11 | f | 1.0 | | 169515 | vector | 10 | 2200 | t | 0.8.0 | | 169843 | vchord | 10 | 2200 | t | 0.3.0 | | (3 rows) ``` As you see, "vchord" has a correct version for Immich Server. 2) Next time, I checked the stack (Immich) in Portainer: ``` .... database: container_name: immich_postgres image: ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0 environment: POSTGRES_PASSWORD: ${DB_PASSWORD} POSTGRES_USER: ${DB_USERNAME} POSTGRES_DB: ${DB_DATABASE_NAME} POSTGRES_INITDB_ARGS: '--data-checksums' # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs # DB_STORAGE_TYPE: 'HDD' volumes: # Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the .env file - ${DB_DATA_LOCATION}:/var/lib/postgresql/data shm_size: 128mb restart: always volumes: model-cache: .... ``` As you see, Its also correct. Community, do you know, what`s wrong with it? Thanks for reading!
20 Replies
Immich
Immich2w ago
:wave: Hey @Mashinist_Сервера_Ka1lie, Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:. References - Container Logs: docker compose logs docs - Container Status: docker ps -a docs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy - Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA Checklist I have... 1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time). 2. :blue_square: read applicable release notes. 3. :blue_square: reviewed the FAQs for known issues. 4. :blue_square: reviewed Github for known issues. 5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy). 6. :blue_square: uploaded the relevant information (see below). 7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable (an item can be marked as "complete" by reacting with the appropriate number) Information In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider: - Your docker-compose.yml and .env files. - Logs from all the containers and their status (see above). - All the troubleshooting steps you've tried so far. - Any recent changes you've made to Immich or your system. - Details about your system (both software/OS and hardware). - Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h). - The version of the Immich server, mobile app, and other relevant pieces. - Any other information that you think might be relevant. Please paste files and logs with proper code formatting, and especially avoid blurry screenshots. Without the right information we can't work out what the problem is. Help us help you ;) If this ticket can be closed you can use the /close command, and re-open it later if needed. [Discussion] v1.133.0 (immich-app/immich#18429)
Mashinist_Сервера_Ka1lie
3) Additional checked PSQL Server logs and see:
2025-09-21 00:00:19.692 UTC [5519] ERROR: deserialization: bad version number

2025-09-21 00:00:19.692 UTC [5519] STATEMENT: with "cte" as (select "asset_faces"."id", "asset_faces"."personId", face_search.embedding <=> $1 as "distance" from "asset_faces" inner join "assets" on "assets"."id" = "asset_faces"."assetId" inner join "face_search" on "face_search"."faceId" = "asset_faces"."id" left join "person" on "person"."id" = "asset_faces"."personId" where "assets"."ownerId" = any($2::uuid[]) and "assets"."deletedAt" is null and ("person"."birthDate" is null or "person"."birthDate" <= $3) order by face_search.embedding <=> $4 limit $5) select * from "cte" where "cte"."distance" <= $6

2025-09-21 15:51:24.587 UTC [11066] ERROR: deserialization: bad version number

2025-09-21 15:51:24.587 UTC [11066] STATEMENT: insert into "smart_search" ("assetId", "embedding") values ($1::uuid, $2) on conflict ("assetId") do update set "embedding" = $3

2025-09-21 15:51:25.425 UTC [11066] ERROR: deserialization: bad version number
2025-09-21 00:00:19.692 UTC [5519] ERROR: deserialization: bad version number

2025-09-21 00:00:19.692 UTC [5519] STATEMENT: with "cte" as (select "asset_faces"."id", "asset_faces"."personId", face_search.embedding <=> $1 as "distance" from "asset_faces" inner join "assets" on "assets"."id" = "asset_faces"."assetId" inner join "face_search" on "face_search"."faceId" = "asset_faces"."id" left join "person" on "person"."id" = "asset_faces"."personId" where "assets"."ownerId" = any($2::uuid[]) and "assets"."deletedAt" is null and ("person"."birthDate" is null or "person"."birthDate" <= $3) order by face_search.embedding <=> $4 limit $5) select * from "cte" where "cte"."distance" <= $6

2025-09-21 15:51:24.587 UTC [11066] ERROR: deserialization: bad version number

2025-09-21 15:51:24.587 UTC [11066] STATEMENT: insert into "smart_search" ("assetId", "embedding") values ($1::uuid, $2) on conflict ("assetId") do update set "embedding" = $3

2025-09-21 15:51:25.425 UTC [11066] ERROR: deserialization: bad version number
Mraedis
Mraedis2w ago
You need to use the compose from that release, this includes the supported postgres images from that time
Mashinist_Сервера_Ka1lie
Hello! Compose from 1.133.0 or 1.132.3? UPD: 1) I've used docker-compose file for 1.32.3 (https://github.com/immich-app/immich/releases/tag/v1.132.3) and deploy - that's OK. 2) Next, I`ve tried to update Immich to 1.133.0 - I met the vchord extension missing error - that's expected from Breaking Changes 1.133.0 3) I edited the compose file like the Breaking Changes Immich 1.133.0 (https://github.com/immich-app/immich/discussions/18429) and deploy - again show the error: Error: The VectorChord extension version is 0.4.3, but Immich only supports >=0.3 <0.4. 4) In Postgres I see again correct versions of extensions fro Immich 1.133.0: oid | extname | extowner | extnamespace | extrelocatable | extversion | extconfig | extcondition --------+---------+----------+--------------+----------------+------------+-----------+-------------- 13766 | plpgsql | 10 | 11 | f | 1.0 | | 169515 | vector | 10 | 2200 | t | 0.8.0 | | 169843 | vchord | 10 | 2200 | t | 0.3.0 | | (3 rows)
Immich
Immich2w ago
[Discussion] v1.133.0 (immich-app/immich#18429)
Mraedis
Mraedis2w ago
From the target release you're upgrading to of course @Mashinist_Сервера_Ka1lie for 1.133.0 the postgres container is ghcr.io/immich-app/postgres:14-vectorchord0.3.0-pgvectors0.2.0
Mashinist_Сервера_Ka1lie
@Mraedis Thanks for your reply! I did it (in screenshot 1). But I also get main mistake (in screentshot 2). I don't understand it because in 1.132.3 I don't have a problem
No description
No description
Mraedis
Mraedis2w ago
Did you toggle "re-pull images" when upgrading in portainer?
Mraedis
Mraedis2w ago
I'll have to wonder whether it's messing up internally somewhere, already having upgraded a database I'm very sure 0.4.3 is supported in later versions so let me check Try jumping to v1.135.3 You just need any version between 133 and 136 so that should be fine
Mashinist_Сервера_Ka1lie
Error: The database currently has VectorChord 0.4.3 activated, but the Postgres instance only has 0.3.0 available.
Mraedis
Mraedis2w ago
Perfect, that means it was already upgraded and is now supported So to complete, change to ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0
Mashinist_Сервера_Ka1lie
@Mraedis Thanks a Lot!
No description
Mashinist_Сервера_Ka1lie
You are the best!
Mraedis
Mraedis2w ago
You just encountered some difficulties by jumping too many versions earlier 🙂
Mashinist_Сервера_Ka1lie
Yep Next time will upgrade my Immich Server earlier:immich:
Mraedis
Mraedis2w ago
That's not the issue, just follow the breaking changes and compose of each of those For vectorchord for instance, you can upgrade but not downgrade
Mashinist_Сервера_Ka1lie
Yep, no problem:)
Immich
Immich2w ago
This thread has been closed. To re-open, use the button below.

Did you find this page helpful?