chore: upgrade to 1.7.0+v2.7.5
Some checks failed
cc-ci/testme cc-ci: failure

This commit is contained in:
autonomic-bot
2026-06-09 15:51:14 +00:00
parent 7eb3937a82
commit f89f82be4e
3 changed files with 63 additions and 1 deletions

1
abra.sh Normal file
View File

@ -0,0 +1 @@
export PG_BACKUP_VERSION=v1

View File

@ -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"
@ -67,6 +67,21 @@ services:
- postgres:/var/lib/postgresql/data
networks:
- backend
deploy:
labels:
backupbot.backup: "${ENABLE_BACKUPS:-true}"
backupbot.backup.pre-hook: "/pg_backup.sh backup"
backupbot.backup.volumes.postgres.path: "backup.sql"
backupbot.restore.post-hook: "/pg_backup.sh restore"
configs:
- source: pg_backup
target: /pg_backup.sh
mode: 0555
configs:
pg_backup:
name: ${STACK_NAME}_pg_backup_${PG_BACKUP_VERSION}
file: pg_backup.sh
secrets:
db_password:

46
pg_backup.sh Executable file
View File

@ -0,0 +1,46 @@
#!/bin/bash
# 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"
# Backup dumps the immich DB to backup.sql (gzip) inside the postgres volume; backupbot archives that
# file. Restore reads it back and reimports.
#
# The immich DB runs the VectorChord/pgvecto.rs extensions. A plain pg_dump emits
# SELECT pg_catalog.set_config('search_path', '', false);
# near the top; on reimport that empty search_path leaves the vector/vchord types + operator classes
# unresolvable, so the first statement that references them errors. immich's official restore
# (docs.immich.app/administration/backup-and-restore) rewrites that line to put `public, pg_catalog`
# back on the search_path BEFORE the import. Without that rewrite a single-transaction import aborts
# wholesale and nothing is restored (the bug in the original ci/pg-backup attempt). We keep
# --single-transaction --set ON_ERROR_STOP=on (immich upstream) so a genuine failure is loud rather
# than silently leaving a half-restored DB.
set -e
BACKUP_FILE='/var/lib/postgresql/data/backup.sql'
export PGPASSWORD=$(cat "${POSTGRES_PASSWORD_FILE:-/run/secrets/db_password}")
DB_USER="${POSTGRES_USER:-postgres}"
DB_NAME="${POSTGRES_DB:-immich}"
function backup {
pg_dump -U "$DB_USER" "$DB_NAME" | gzip > "$BACKUP_FILE"
}
function restore {
# immich-server holds TCP connections to the DB; terminate them so DROP DATABASE can proceed
# (the matrix-synapse pg_hba "local trust" trick does not cover networked connections).
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"
# Rewrite the empty search_path the VectorChord dump sets so vector/vchord type + operator
# references resolve during the import (immich upstream restore procedure), then import.
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" --single-transaction --set ON_ERROR_STOP=on
}
$@