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

@@ -1,14 +1,11 @@
 #!/bin/bash
 
-# Postgres backup/restore hook for the immich `database` service (VectorChord/pgvecto.rs image).
+# Postgres backup/restore hook for immich's VectorChord/pgvecto.rs `database` service.
-# Invoked by backupbot-two via the deploy labels:
+# Two image-specific constraints:
-#   backupbot.backup.pre-hook    = "/pg_backup.sh backup"
+#   1. Never DROP DATABASE — the bundled pgvecto.rs worker PANICs and crashes the server.
-#   backupbot.backup.volumes.postgres.path = "backup.sql"
+#      So `pg_dump --clean --if-exists` does a per-object replace in the live DB on restore.
-#   backupbot.restore.post-hook  = "/pg_backup.sh restore"
+#   2. Restore rewrites the dump's empty search_path back to `public, pg_catalog` so VectorChord
-# Backup dumps the immich DB to backup.sql (gzip) inside the postgres volume; backupbot then
+#      types resolve (per https://docs.immich.app/administration/backup-and-restore).
-# 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).
 
 set -e
 
@@ -18,16 +15,13 @@ DB_USER="${POSTGRES_USER:-postgres}"
 DB_NAME="${POSTGRES_DB:-immich}"
 
 function backup {
-  pg_dump -U "$DB_USER" "$DB_NAME" | gzip > "$BACKUP_FILE"
+  pg_dump --clean --if-exists -U "$DB_USER" "$DB_NAME" | gzip > "$BACKUP_FILE"
 }
 
 function restore {
-  # immich-server holds connections to the DB; drop them so DROP DATABASE can proceed.
+  gunzip -c "$BACKUP_FILE" \
-  psql -U "$DB_USER" -d postgres -c \
+    | sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
-    "SELECT pg_terminate_backend(pid) FROM pg_stat_activity WHERE datname='${DB_NAME}' AND pid<>pg_backend_pid();"
+    | psql -U "$DB_USER" -d "$DB_NAME" -f -
-  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 -
 }
 
 $@