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

@@ -19,21 +19,18 @@ services:
       - proxy
       - backend
     healthcheck:
-      test: ["CMD-SHELL", "immich-healthcheck"]
-      start_period: 120s
+      disable: false
     depends_on:
       - redis
       - database
     deploy:
-      update_config:
-        failure_action: continue
       labels:
         - "traefik.enable=true"
         - "traefik.http.services.${STACK_NAME}.loadbalancer.server.port=2283"
         - "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.8.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"
@@ -57,7 +54,7 @@ services:
       - backend
 
   database:
-    image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.3.0@sha256:87c050465fb969a68c7ac23e375e21f4c95cfacd0edce5fa1bc31e63b7891891
+    image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:bcf63357191b76a916ae5eb93464d65c07511da41e3bf7a8416db519b40b1c23
     environment:
       POSTGRES_PASSWORD_FILE: /run/secrets/db_password
       POSTGRES_USER: ${DB_USERNAME}

pg_backup.sh

@@ -1,11 +1,22 @@
 #!/bin/bash
 
-# Postgres backup/restore hook for immich's VectorChord/pgvecto.rs `database` service.
-# Two image-specific constraints:
-#   1. Never DROP DATABASE — the bundled pgvecto.rs worker PANICs and crashes the server.
-#      So `pg_dump --clean --if-exists` does a per-object replace in the live DB on restore.
-#   2. Restore rewrites the dump's empty search_path back to `public, pg_catalog` so VectorChord
-#      types resolve (per https://docs.immich.app/administration/backup-and-restore).
+# 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.volumes.postgres.path = "backup.sql"
+#   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
 
@@ -15,7 +26,7 @@ DB_USER="${POSTGRES_USER:-postgres}"
 DB_NAME="${POSTGRES_DB:-immich}"
 
 function backup {
-  pg_dump --clean --if-exists -U "$DB_USER" "$DB_NAME" | gzip > "$BACKUP_FILE"
+  pg_dump -U "$DB_USER" "$DB_NAME" | gzip > "$BACKUP_FILE"
 }
 
 function restore {