-
Notifications
You must be signed in to change notification settings - Fork 207
Issues: EnterpriseDB/barman
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
barman-cloud-backup does not support zstd
feature request
triage
#1083
opened Apr 30, 2025 by
FF-Ninja
barman-wal-restore uses only one of several ssh connections for get-wal
#1080
opened Apr 16, 2025 by
NeiNGuNa
Issue with object storage when sse-s3 is not supported. Can we make this optional (is sse-c an option?)
#1071
opened Mar 6, 2025 by
chris-milsted
PosgreSQLConnection.fetch_remote_status Issue With Large PostgreSQL
triage
#1056
opened Jan 17, 2025 by
gariels
Don't fail if the replication slots already exists during creation
feature request
triage
#1049
opened Dec 30, 2024 by
antonag32
Barman postgres restore on different server failing due to "unable to prepare 'XXX' tablespace"
moreinfo
question
#1048
opened Dec 22, 2024 by
adam-shenker
barman backup <server> --wait
not working with Postgres 17
triage
#1041
opened Dec 12, 2024 by
cameronmurdoch
barman streaming replication stops working after switchover - normal wal archival continues to work
#1035
opened Nov 29, 2024 by
thoro
Backup fails for DBs 'Barman cloud WAL archive check exception: SSL validation failed'
#1031
opened Nov 1, 2024 by
zoe-tek
Support custom values for recovery options when running
barman recover
enhancement
#956
opened Jul 3, 2024 by
barthisrael
Collecting ideas on how to speed up recovery
enhancement
performance
#943
opened Jun 20, 2024 by
toydarian
barman-cloud-restore encount read timeout when restore from azure blob
#907
opened Mar 9, 2024 by
litaocdl
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.