Arch Linux User Repository

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

From v1.111.0, this package does not build with nodejs < v20.

I'm unable to start my immich server due to the following error around the upload/encoded-video/.immich file

Jan 27 21:00:07 desktop immich-server[1494334]: [Nest] 1494334  - 01/27/2025, 9:00:07 PM     LOG [Api:StorageService] Verifying system mount folder checks, current state: {"mountChecks":{"thumbs":true,"upload":true,"backups":true,"library":true,"profile":true,"encoded-video":true}}
Jan 27 21:00:07 desktop immich-server[1494334]: [Nest] 1494334  - 01/27/2025, 9:00:07 PM   ERROR [Api:StorageService] Failed to write /mnt/storage/Servers/immich-media/upload/encoded-video/.immich: Error: EROFS: read-only file system, open '/mnt/storage/Servers/immich-media/upload/encoded-video/.immich'

I'm running a ZFS pool that these files are stored on. It was working at install, but after an update a month or so ago, it hasn't worked. I also had some trouble with the postgres update, and I've reinstalled it a couple times, so maybe one of my configs got out of wack, but I'd be happy to see if there's any ideas as to what might be causing this.

EDIT: I had to update the service file with the new path with the following change using systemctl edit immich-server.service:

[Service]
ReadWritePaths=/tmp /var/tmp /mnt/storage/Servers/immich-media/upload

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

Just removed my forced downgrade, and had postgresql-old-upgrade installed. This fixed the upgrade issue I had before. It handled the upgrade process on the fly when upgrading :) All good now.

[EDIT] Seems like it didn't work after a reboot. Still version error, and run into same issue as @CountMurphy when trying to upgrade the database. Postgresql is a but of a nightmare to work with it seems.

Has anyone got the upgrade to work? I've updated the pgvecto.rs-immich-bin for postgres 17, copied the old vectors.so into /opt/pgsql-16/lib, but when I run pg_upgrade I get

pg_restore: error: could not execute query: ERROR: could not find function "_vectors_vecf16_operator_cosine_wrapper" in file "/usr/lib/postgresql/vectors.so"

Never had to upgrade postgres before, so might be missing something basic?

EDIT: Update was successful using the manual dump and reload method

@zynex pgvecto.rs-immich-bin has been updated a few hours ago and now works with postgres v17.

Mind that if you're using that package, you need the vectors extension, not the vector extension. Slight difference.

Noticed that PostgreSQL was updated to v17 today, and broke everything. Tried upgrading the database, but there is some error finding vector.so while trying to upgrade the database, so had to downgrade the system update and fix it to 2025-01-11 to prevent upgrading PostgreSQL. Seems that pgvector >=0.4.0 isn't supported by Immich yet either (got and error when trying).

Thanks @pikl

v1.124.1-1 includes a dependency for python312 and should fix build problems since Arch went to Python 3.13

There's a python-onnx package I'm using

I'll try that as well then, thank you. Still python-onnx that is not compiling with python 3.13, is that needed? Is it installed on your system?