From: pgstef (@pgstef) <noreply+pgstef@github.com>
To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>
Subject: Re: [pgbackrest/pgbackrest] PR #2898: Add stanza-rekey command to change the repository passphrase.
Date: Fri, 06 Nov 2026 20:48:53 +0000
Message-ID: <gh-pgbackrest-pgbackrest-2898-c6695155577@github.com> (raw)
In-Reply-To: <gh-pgbackrest-pgbackrest-2898@github.com>
References: <gh-pgbackrest-pgbackrest-2898@github.com>
> Here's a better implementation at [6d189c9](https://github.com/pgbackrest/pgbackrest/commit/6d189c9776f09807d78783b16134fdca482faa14). This preserves the prior key on save and only rekey updates it. I'll have another look at it on Monday but I think this is the way to go.
Yes, with this fix, it looks like a host configured with only the old passphrase can continue archiving and backing up, even after a backup or an `expire` that removes a backup is run on a host configured with both the new and old passphrases.
After `stanza-rekey`, the old host loses access as documented, and everything works again once its configuration is updated. The new `check` message also looks accurate.
Looks good to me now! :-)