Arch Linux User Repository

is it possible to ship pre-built package?

Upstream recommends using docker, for which they have pre-built images (that might also work with podman).

PostgreSQL 18 is coming to the Arch repos. Before upgrading, backup the files for vectorchord and pgvector somewhere, and then follow https://wiki.archlinux.org/title/PostgreSQL#Upgrading_PostgreSQL instructions. (In the next release, I'll also update the postinstall message to recommend changing postgresql.conf instead of doing ALTER SYSTEM SET.)

Also, you may find yourself updating VectorChord in this process. When doing so, remember to follow the migration steps at https://docs.immich.app/administration/postgres-standalone/#updating-vectorchord .

immich-web (localhost/immich-server:2283) used to be broken for some users of this package.

As @yparitcher also noticed, this was most likely caused by the following additions to .gitignore from f4e0aad2c495, which have since be reverted:

src/
pkg/
*.pkg.tar.zst
LICENSES/

The reason—for both this change sometimes and unpredictably breaking the build, and builds under a clean chroot still working—is unknown. I meant to investigate this on 2025-08-19 while updating the package but called it a day due to the unpredictability and long time of building. Help with figuring out why this happened would be greatly appreciated.

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.

@riaqn I've fixed the valkey issue by committing to the valkey Arch package; the problem should go away in the next release/pkgrel of it!

@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