0.133.0 tries to DROP VectorChord extension instead of using it
I have external Postgres instance. Followed upgrade to VectorChord procedure. During first startup I got:
LOG [Api:DatabaseRepository] Dropping VectorChord extension
Why is it behaving like this instead of migrating database to new extension?
This is Kubernetes self-managed installation but I don't think it makes any difference while using external database.
9 Replies
:wave: Hey @daftu,
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. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: 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.
Successfully submitted, a tag has been added to inform contributors. :white_check_mark:Please post more detail like requested
I think I've found it. It's because of DB_VECTOR_EXTENSION environment variable which has to be changed when migrating to VectorChord.
It wasn't mentioned in migration instructions (who remember that this exists? :)).
Maybe it's worth documenting in the migration procedure?
IMO it has to be definitely mentioned somewhere there: https://immich.app/docs/administration/postgres-standalone/#updating-vectorchord
It doesn’t “need” to be changed in that the server will just use pgvector and nothing will break, but yes it’s an oversight that the pgvector section doesn’t mention this since any pgvector user up till now would have that env set
The new behavior is essentially that it’ll automatically choose the best extension available in the DB, and the env is an override to choose a specific one when there are multiple available
It reindexes from one extension to the other and drops any now-unnecessary extensions
That env is set in situation, when using external database on Debian based OS where there is no (or I couldnt easily install it in the pass) pgvecto.rs extension, but pgvector. Then you have to set DB_VECTOR_EXTENSION with "pgvector" (I think "pgvecto.rs" is the default and doesnt need to be set).
According to what you've said that "it doesnt <need> to be changed in that the server will just use pgvector anothing will break" hey, but this is migration instruction how to MIGRATE to VectorChord, so it has to be changed. I was not using this docs to stay with pgvector 🙂
lol you’ve got me there
And this is just one day after releasing 0.133.0, I think other users will face this issue as well.
Finally - it's working now. Nice work guys! Brilliant software 🙂
"Sneak peak" sounds promising. This is the missing part, because currently iOS app is unusable with my 67k+ photos/videos.
#18508 should make this clearer
[Pull Request] fix(docs): mention
DB_VECTOR_EXTENSION env in pgvector->vchord migration guide (immich-app/immich#18508)