From: dwsteele (@dwsteele) <noreply+dwsteele@github.com>
To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>
Subject: Re: [pgbackrest/pgbackrest] issue #2919: Question: archive-get fails on a standby with an unused pg2-host
Date: Fri, 13 Nov 2026 14:15:09 +0000
Message-ID: <gh-pgbackrest-pgbackrest-2919-c6855488366@github.com> (raw)
In-Reply-To: <gh-pgbackrest-pgbackrest-2919@github.com>
References: <gh-pgbackrest-pgbackrest-2919@github.com>
> Is it deliberate that the check also applies to archive-get and archive-push, which do not use the remote pg host?
The check that is causing this error runs during config and is run for all commands even though it was written specifically for backup, because backup might be run on this host and then it would fail.
We could add an exception for archive-get but that is additional code and tests for a scenario that we do not think is a good practice. If the repo is physically located on the primary then that is bad practice because you can lose the primary and the backup repo at the same time. If the repo is located on NFS or some other remote system but only accessed through the primary then that is still a bad idea because if makes a the primary a single point of failure for archiving. In this case it is more robust to mount the remote storage on the standby directly.
The `--reset-*` options exist exactly for the purpose of getting around our internal rules for unusual configurations. And yes, I do consider this to be an unusual configuration. If you really see it everywhere then that is concerning.
> Is a pgN-host ever legitimate on a PostgreSQL host that uses a remote repository?
In general I would say no -- because doing so by definition makes that host a repo host. Now you have a repo host referring to a repo host, which is confusing and increases network traffic. Best practices exist not only to make backups sane but to make restores sane as well. Complex configurations make disaster recovery less reliable.
> Would you accept an error message that names the options involved?
I'm not sure what that would look like or if it would be helpful but if you have ideas I'm happy to review them.
> Since 2.55.0 the backup command can operate on remote repositories.
The part that is unsupported here is placing the repository on the primary (but of course you can make it work with `--reset-pgX-host`). We feel this is bad practice and try to discourage it.