Arch Linux User Repository

You may notice pacman refuse to upgrade this package, saying warning: cannot resolve "vectorchord", a dependency of "immich-server".

This is due to required manual intervention within the immich server database.

Newer versions of immich server have deprecated pgvecto.rs in favor of vectorchord.

Before updating from 1.133.1 or older, please follow steps 1 and 2 of the manual migration steps (should be the second dropdown) at https://immich.app/docs/administration/postgres-standalone/#migrating-to-vectorchord and uninstall pgvecto.rs.

Remember to remove references to "vectors.so" (which is shipped by pgvecto.rs) in shared_preload_libraries before pgvecto.rs in uninstalled. (For vectorchord to work, you'll need to add "vchord.so" to shared_preload_libraries after the upgrade as well.)

After that, you may upgrade this package. Please remember to follow steps 4 and 5 of the manual migration steps after the upgrade is finished to prevent data loss.

Upgrading to postgresql-17 is awkward because of pgvecto.rs if you have been using 0.2.0 as provided by AUR package pgvecto.rs-immich. If you have been using 0.3.0 as provided by AUR package pgvecto.rs-immich-bin then these extra steps are likely not required and I suggest the wiki instructions for upgrades for major version increments of postgresql are followed.

If you would like to stick at postgresql-16 please add the following to pacman.conf:

IgnorePkgs = postgresql postgresql-libs

Following the manual dump and reload in the wiki does appear to work, with a few extra steps to consider the pgvecto.rs upgrade.

Starting point is postgresql-old-upgrade installed with pgvector.rs-0.2.0. Symlink the installation outputs of pgvecto.rs into the directories used by the parallel installation of postgresql-old-upgrade.

ln -s /usr/share/postgresql/extension/vectors.control /opt/pgsql-16/share/extension/vectors.control
ln -s /usr/share/postgresql/extension/vectors--0.2.0.sql /opt/pgsql-16/share/extension/vectors--0.2.0.sql
ln -s /usr/lib/postgresql/vectors.so /opt/pgsql-16/lib/vectors.so

Then perform the database start (/opt/psql-16/bin/pg_ctl .. start), "dump" (pg_dumpall...) and database stop (/opt/psql-16/bin/pg_ctl .. start) steps in the wiki.

Upgrade to postgresql-17 and pgvecto.rs-0.3.0 (provided by pgvector.rs-immich-bin). Clear out /var/lib/postgresql/data then initialise the database (initdb...) as per the wiki.

Start the service using systemctl start postgresql and install the pgvecto.rs using the following command:

psql -c 'ALTER SYSTEM SET shared_preload_libraries = "vectors.so"'

Finally restart the postgresql service and perform the reload (psql...) steps in the wiki.

EDITED: Various clarifications

@riaqn Weird, the valkey service already includes redis as an alias. In theory it should already work. I'll look into it

We need to change Requires=redis.service to valkey.service.

Oh yeah, that's also what I had to do; one wouldn't encounter that problem if they ALTER_SYSTEM_SET while the appropriate files are still installed. I thought it was just me being stupid lol; since it's not, I've added a reminder to the pinned instructions.

Just completed the migration to vectorchord. All went smooth minus one bit. If you originally ran sudo -u postgres psql -c 'ALTER SYSTEM SET shared_preload_libraries = "vectors.so"' as I did when installing the previous version, postgres will not restart due to missing vectors.so.

The fix was pretty straight forward: in your postgres data directory, edit the file postgresql.auto.conf and replace vectors.so with vchord.so and restart postgres.

You may notice pacman refuse to upgrade this package, saying warning: cannot resolve "vectorchord", a dependency of "immich-server".

This is due to required manual intervention within the immich server database.

Newer versions of immich server have deprecated pgvecto.rs in favor of vectorchord.

Before updating from 1.133.1 or older, please follow steps 1 and 2 of the manual migration steps (should be the second dropdown) at https://immich.app/docs/administration/postgres-standalone/#migrating-to-vectorchord and uninstall pgvecto.rs.

Remember to remove references to "vectors.so" (which is shipped by pgvecto.rs) in shared_preload_libraries before pgvecto.rs in uninstalled. (For vectorchord to work, you'll need to add "vchord.so" to shared_preload_libraries after the upgrade as well.)

After that, you may upgrade this package. Please remember to follow steps 4 and 5 of the manual migration steps after the upgrade is finished to prevent data loss.

hola soy vuestro mantenedor nuevo

I'm planning to migrate to vectorchord instead of pgvecto.rs in the next update. This probably requires manual intevention, which could be automated if I knew your postgresql home directory and password, which means it can't be automated. I think this should be how the next version of this AUR package should be released as this AUR package has not been updated in a month, and releasing a long-awaited update is a great way for users to pay attention and clue them in to needed manual intervention, I think. I'll figure out the best way to approach this as soon as possible.

I'm planning to adopt the package. Pikl disowned after I filed the orphan request, but we still have to wait another week before the request processors remove wabi from the list of maintainers as well.

@jettscythe it is working just fine if you change the version in the PKGBUILD to current one, even with vectorchord 0.4.2, which is now supported

upstream is now at v1.135.0

Looks like V1.133.0 switched from pgvecto to VectorChord, but the current PKG files do not have that listed as a dependency. Keeping pgvecto will work for now, but a future release will remove support for it.