-
Notifications
You must be signed in to change notification settings - Fork 193
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 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
TypeError: '<=' not supported between instances of 'str' and 'NoneType'
enhancement
triage
#1026
opened Oct 21, 2024 by
coroneltortuga
Add information about the model which is active is
barman status
and barman show-server
triage
#1022
opened Oct 10, 2024 by
martinmarques
Make
BACKUP_ID
optional when performing PITR with barman-cloud-restore
enhancement
triage
#1013
opened Sep 10, 2024 by
gbartolini
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
pg archive 100% full not able to delete the archive wal files
help wanted
#917
opened Mar 26, 2024 by
shafiulla123
How can I set parameter statement_timeout in barman backup configuration file ?
#915
opened Mar 25, 2024 by
Myshiner
barman-cloud-restore encount read timeout when restore from azure blob
#907
opened Mar 9, 2024 by
litaocdl
ERROR: WAL synchronisation for server XY failed with: Expected 2 arguments, got 1
#906
opened Feb 29, 2024 by
eoener-tpgroup
Questions on wal_retention_policy / removal of WAL files that are not required
question
#902
opened Feb 21, 2024 by
phebing
Previous Next
ProTip!
Follow long discussions with comments:>50.