Search results

Geographical Redundancy and restore from the secondary barman node

Status: Open.

#1102 In EnterpriseDB/barman;

· dblugeon opened on Jul 29, 2025

Reducing expensive S3 operations

triage

Status: Open.

#1101 In EnterpriseDB/barman;

· CppBunny opened on Jul 27, 2025

barman-cloud-restore from s3 fails with: Barman cloud restore exception: An error occurred while reading from response stream:

Status: Open.

#1100 In EnterpriseDB/barman;

· piotr1212 opened on Jul 16, 2025

Using the raw full basebackup for restore, without associated WALs

Status: Open.

#1099 In EnterpriseDB/barman;

· mojtabash78 opened on Jul 16, 2025

Improve barman to fully use local loggers

Status: Open.

#1097 In EnterpriseDB/barman;

· ethiebautgeorge-nasuni opened on Jul 15, 2025

Missing pg_combinebackup produces less than helpful error message

bug

next release

Status: Open.

Bug

#1096 In EnterpriseDB/barman;

· avandras opened on Jul 14, 2025

barman-cloud-wal-archive: authenticationerrordetail:Signed Directory Depth Invalid

Status: Open.

#1092 In EnterpriseDB/barman;

· Anhui-tqhuang opened on Jul 1, 2025

barman-cloud-backup does not support zstd

feature request

triage

Status: Open.

#1083 In EnterpriseDB/barman;

· FF-Ninja opened on Apr 30, 2025

barman-wal-restore uses only one of several ssh connections for get-wal

moreinfo

question

Status: Open.

#1080 In EnterpriseDB/barman;

· NeiNGuNa opened on Apr 16, 2025

[Feature] restore_command avoid sudo -u barman

triage

Status: Open.

#1075 In EnterpriseDB/barman;

· kapouer opened on Mar 28, 2025

default label with variables

Status: Open.

#1072 In EnterpriseDB/barman;

· maletin opened on Mar 16, 2025

Issue with object storage when sse-s3 is not supported. Can we make this optional (is sse-c an option?)

Status: Open.

#1071 In EnterpriseDB/barman;

· chris-milsted opened on Mar 6, 2025