pg.ddx.io  pgbackrest/pgbackrest GitHub issues and pull requests  
help / color / mirror / Atom feed
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 14:32:04 +0000
Message-ID: <gh-pgbackrest-pgbackrest-2919-c6826450793@github.com> (raw)
In-Reply-To: <gh-pgbackrest-pgbackrest-2919@github.com>
References: <gh-pgbackrest-pgbackrest-2919@github.com>

The problem here is that you're using an unsupported architecture.

> A standby whose repository is hosted on the primary.

That's where the problem starts.

The distinction between a repository host and a PostgreSQL host is important:

- The **repository host**, where the repository is local and PostgreSQL hosts are remote, is responsible for initiating backups.
- The **PostgreSQL host**, where PostgreSQL is local, runs commands such as `restore`, `archive-push`, and `archive-get`. These commands don't need a remote PostgreSQL host configured.

You're hitting this restriction because you're trying to use the same configuration as both a repository host and a PostgreSQL host. That's not a supported setup, regardless of whether a particular command actually uses the remote PostgreSQL host.

As already discussed in #1832, these are two different roles that should not be mixed.

If you want to access a repository hosted elsewhere and initiate backups from the standby, you should use another repository access method, such as NFS or SFTP, rather than combining `repo1-host` and `pg2-host`.

The ability to run backups against remote repositories introduced in 2.55.0 doesn't change this restriction.

Finally, regarding:

> Would you accept an error message that names the options involved?

I wouldn't be in favor of that. This error can be triggered by many different combinations of options, and trying to enumerate all possible cases would add complexity without addressing the underlying issue. The current message already identifies the configuration conflict: PostgreSQL and repository hosts cannot both be configured as remote.

view thread (12+ messages)  latest in thread

Message-ID: <gh-pgbackrest-pgbackrest-2919-c6826450793@github.com>
Permalink:  ../gh-pgbackrest-pgbackrest-2919-c6826450793@github.com/

 · 


This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox