From: pgstef (@pgstef) <noreply+pgstef@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: Thu, 12 Nov 2026 15:23:55 +0000
Message-ID: <gh-pgbackrest-pgbackrest-2919-c6827755823@github.com> (raw)
In-Reply-To: <gh-pgbackrest-pgbackrest-2919@github.com>
References: <gh-pgbackrest-pgbackrest-2919@github.com>
> I don't agree. It should be. I see it everywhere.
We already discussed this in #1832, and my opinion hasn't changed.
`repo-host` and `pg-host` serve two different purposes and use cases. They shouldn't be mixed simply because a particular setup happens to be used elsewhere. Just because you see something deployed in many places doesn't necessarily mean it's a good design or that pgBackRest should accommodate it.
More importantly, I would strongly advise against storing your backup repository on the same host as your primary database. In my opinion, that's a very poor backup architecture. You're putting your backups in the same failure domain as the database you're trying to protect. Losing the primary could mean losing your backups as well. A dedicated repository host or independent remote storage would be a much more sensible design.
You asked for feedback from maintainers, and I've shared my perspective as a pgBackRest contributor, just as I did in #1832. You're obviously free to disagree with it, but repeatedly asking the same question won't change my answer. And frankly, revisiting the same discussion after feedback has already been provided doesn't particularly encourage me to keep spending time answering your issues.