Skip to content

fix: log transient connectivity errors during WAL restore - #1112

Merged
mnencia merged 2 commits into
mainfrom
dev/1111
Sep 29, 2026
Merged

mnencia merged 2 commits into
mainfrom
dev/1111

Conversation

@gbartolini

Copy link
Copy Markdown
Contributor

Requires Barman 3.20.0

Closes #1111

@gbartolini
gbartolini requested a review from a team as a code owner September 22, 2026 09:18
gbartolini and others added 2 commits September 29, 2026 20:32
Requires Barman 3.20.0

Closes #1111

Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
The comment above the first-WAL error check still said the failure is
only logged by RestoreList, and the version note implied exit code 2 is
new in Barman 3.20.0, while what changed there is that transient network
errors are now reported with that exit code.

Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>
@mnencia
mnencia merged commit 01637c9 into main Sep 29, 2026
9 checks passed
@mnencia
mnencia deleted the dev/1111 branch September 29, 2026 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Intercept transient network errors with barman-cloud-wal-restore

4 participants