From 40e8ef0c7082700bf787508f48b88a9114e4b3f2 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Wed, 16 Nov 2022 11:50:02 +0200 Subject: [PATCH] Do not tell people to use latest Borgmatic - it won't help with Postgres v15 Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2259#issuecomment-1312737960 --- docs/maintenance-postgres.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/maintenance-postgres.md b/docs/maintenance-postgres.md index d22b1648..1b848703 100644 --- a/docs/maintenance-postgres.md +++ b/docs/maintenance-postgres.md @@ -81,8 +81,6 @@ This playbook can upgrade your existing Postgres setup with the following comman ansible-playbook -i inventory/hosts setup.yml --tags=upgrade-postgres **Warning: If you're using Borg Backup keep in mind that there is no official Postgres 15 support yet.** -As long as Alpine Linux is missing packages for postgres15, it is possible to use the `latest` or `14` image of borgmatic. Edit your `vars.yml` and add: -`matrix_backup_borg_version: "latest"` **The old Postgres data directory is backed up** automatically, by renaming it to `/matrix/postgres/data-auto-upgrade-backup`. To rename to a different path, pass some extra flags to the command above, like this: `--extra-vars="postgres_auto_upgrade_backup_data_path=/another/disk/matrix-postgres-before-upgrade"`