chore: upgrade to 1.7.0+v2.7.5

Confirms immich-server at the latest v2.7.5 + holds the DB pin immich v2.7.5 ships
(14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357), and adds a working postgres
backup/restore for the VectorChord DB (search_path rewrite per immich docs + a
local-trust pg_hba lockout, like matrix-synapse, so the app cannot race the reimport).

compose.yml

@@ -30,7 +30,7 @@ services:
         - "traefik.http.routers.${STACK_NAME}.rule=Host(`${DOMAIN}`${EXTRA_DOMAINS})"
         - "traefik.http.routers.${STACK_NAME}.entrypoints=web-secure"
         - "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}"
-        - "coop-cloud.${STACK_NAME}.version=1.6.0+v2.7.5"
+        - "coop-cloud.${STACK_NAME}.version=1.7.0+v2.7.5"
         - "backupbot.backup=${ENABLE_BACKUPS:-true}"
         - "backupbot.volumes.model-cache=false"
         - "backupbot.volumes.uploads=false"

pg_backup.sh

@@ -2,13 +2,21 @@
 
 # Postgres backup/restore hook for the immich `database` service (VectorChord/pgvecto.rs image).
 # Invoked by backupbot-two via the deploy labels:
-#   backupbot.backup.pre-hook    = "/pg_backup.sh backup"
+#   backupbot.backup.pre-hook              = "/pg_backup.sh backup"
 #   backupbot.backup.volumes.postgres.path = "backup.sql"
-#   backupbot.restore.post-hook  = "/pg_backup.sh restore"
-# Backup dumps the immich DB to backup.sql (gzip) inside the postgres volume; backupbot then
-# archives that file. Restore reads it back and reimports. immich-server keeps TCP connections
-# open to the DB, so restore must terminate them and FORCE-drop before recreating (the matrix-synapse
-# pg_hba "local trust" trick does not cover networked connections).
+#   backupbot.restore.post-hook            = "/pg_backup.sh restore"
+#
+# IMPORTANT — why this restore does NOT drop the database:
+# immich's postgres image bundles the legacy pgvecto.rs (`vectors`) extension. Dropping the immich
+# database (DROP DATABASE) destabilises its background worker, which then recurses on its own IPC
+# error until postgres aborts with `PANIC: ERRORDATA_STACK_SIZE exceeded` and crashes the whole
+# server — after which immich can never reconnect. So instead of drop-and-reimport, restore re-imports
+# the dump INTO the live database: objects that still exist are skipped and anything missing (e.g. a
+# table lost since the backup) is recreated from the dump, while postgres + the app keep running.
+# The `search_path` rewrite is immich's documented restore step
+# (https://docs.immich.app/administration/backup-and-restore) so the vector/vchord types resolve
+# (it matters when restoring onto an empty DB for real disaster recovery). ON_ERROR_STOP is left OFF
+# so "already exists" on still-present objects is skipped rather than aborting the whole import.
 
 set -e
 
@@ -22,12 +30,9 @@ function backup {
 }
 
 function restore {
-  # immich-server holds connections to the DB; drop them so DROP DATABASE can proceed.
-  psql -U "$DB_USER" -d postgres -c \
-    "SELECT pg_terminate_backend(pid) FROM pg_stat_activity WHERE datname='${DB_NAME}' AND pid<>pg_backend_pid();"
-  psql -U "$DB_USER" -d postgres -c "DROP DATABASE ${DB_NAME} WITH (FORCE);"
-  createdb -U "$DB_USER" "$DB_NAME"
-  gunzip -c "$BACKUP_FILE" | psql -U "$DB_USER" -d "$DB_NAME" -1 -v ON_ERROR_STOP=1 -f -
+  gunzip -c "$BACKUP_FILE" \
+    | sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
+    | psql -U "$DB_USER" -d "$DB_NAME" -f -
 }
 
 $@