pg.ddx.io  pgbackrest/pgbackrest GitHub issues and pull requests  
help / color / mirror / Atom feed
From: NoobInTheNet (@NoobInTheNet) <noreply+NoobInTheNet@github.com>
To: pgbackrest/pgbackrest <noreply+pgbackrest-pgbackrest@github.com>
Subject: Re: [pgbackrest/pgbackrest] issue #2926: Async archive-push no longer pushes ahead to a healthy repository when another repository fails (2.60.1 vs 2.58.0)
Date: Tue, 17 Nov 2026 17:07:56 +0000
Message-ID: <gh-pgbackrest-pgbackrest-2926-c6955160340@github.com> (raw)
In-Reply-To: <gh-pgbackrest-pgbackrest-2926@github.com>
References: <gh-pgbackrest-pgbackrest-2926@github.com>

I have now run the same script on Linux (aarch64, kernel 6.18, PostgreSQL 17.11, inside a Nix build sandbox), so the limit in point 3 above no longer applies. The result matches macOS:

| Version | New segments in repo1 | Async log |
| --- | --- | --- |
| 2.58.0 | 12 of 12 | no run stopped early |
| 2.60.1 | 3 of 12 | 20 runs logged `stopped archive-push after an error`; nothing after `...0B` reached repo1 |

Both binaries were built from the release tags with the nixpkgs package definition.


view thread (9+ messages)  latest in thread

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