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

Thanks, but this answer is not satisfactory: it restates the implemented behavior, which is already described in the issue (the check in `src/config/load.c`, the test with a higher pg index, the sentence from the user guide).

My questions are about intent, so I would appreciate an answer from a maintainer:

1. Is it deliberate that the check also applies to `archive-get` and `archive-push`, which do not use the remote pg host?
2. Is a `pgN-host` ever legitimate on a PostgreSQL host that uses a remote repository?
3. Would you accept an error message that names the options involved?
4. Since 2.55.0 the `backup` command can operate on remote repositories. With the repository hosted on the primary, running a backup from the standby (`backup-standby=y`) needs both `pg2-host` (the primary) and `repo1-host` (also the primary) in the standby configuration, and the same check rejects it with `[027]` (tested with 2.59.0). Is this setup meant to be unsupported, so that the backup has to be started from the primary?

view thread (12+ messages)  latest in thread

Message-ID: <gh-pgbackrest-pgbackrest-2919-c6825800246@github.com>
Permalink:  ../gh-pgbackrest-pgbackrest-2919-c6825800246@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