From 1d9c844cadd15ced4bc2451b4142bff75c8c0d1b Mon Sep 17 00:00:00 2001 From: Danny Groenewegen Date: Sun, 2 Aug 2026 17:02:40 +0200 Subject: [PATCH] fix: remove -c max_connections flag from postgres command to fix pgautoupgrade The pgautoupgrade switch from 13.1.0+32.0.11-fpm was released untested and had a bug: the db service's `-c max_connections=...` command breaks pgautoupgrade, failing with `initdb: invalid option -- 'c'`. See pgautoupgrade/docker-pgautoupgrade#148 --- compose.postgres.yml | 3 ++- compose.yml | 2 +- release/next | 2 ++ 3 files changed, 5 insertions(+), 2 deletions(-) create mode 100644 release/next diff --git a/compose.postgres.yml b/compose.postgres.yml index cee110c..777f9df 100644 --- a/compose.postgres.yml +++ b/compose.postgres.yml @@ -11,7 +11,8 @@ services: db: image: "pgautoupgrade/pgautoupgrade:14-debian" - command: -c "max_connections=${MAX_DB_CONNECTIONS:-100}" + #setting max_connections with -c breaks pgautoupgrade + #command: -c "max_connections=${MAX_DB_CONNECTIONS:-100}" volumes: - "postgres:/var/lib/postgresql/data" networks: diff --git a/compose.yml b/compose.yml index 55cb91c..d974851 100644 --- a/compose.yml +++ b/compose.yml @@ -95,7 +95,7 @@ services: failure_action: rollback order: start-first labels: - - "coop-cloud.${STACK_NAME}.version=13.1.1+32.0.12-fpm" + - "coop-cloud.${STACK_NAME}.version=13.1.1+32.0.13-fpm" - "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT}" - "backupbot.backup=${ENABLE_BACKUPS:-true}" - "backupbot.backup.volumes.redis=false" diff --git a/release/next b/release/next new file mode 100644 index 0000000..d71cfdc --- /dev/null +++ b/release/next @@ -0,0 +1,2 @@ +Important: +The pgautoupgrade switch from 13.1.0+32.0.11-fpm was released untested and had a bug: the db service's `-c max_connections=...` command breaks pgautoupgrade, failing with `initdb: invalid option -- 'c'`. If your db got stuck mid-upgrade on 13.1.0-13.1.4 with that error: restore the old data dir and remove the upgrade lock file. Then redeploy this version. -- 2.52.0