-
Notifications
You must be signed in to change notification settings - Fork 191
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
Make
BACKUP_ID
optional when performing PITR with barman-cloud-restore
enhancement
triage
#1013
opened Sep 10, 2024 by
gbartolini
barman-cloud-backup-list and barman-cloud-backup-show return incorrect time if postgres is not in utc 0
bug
triage
#1009
opened Aug 28, 2024 by
litaocdl
Add "AWS Snapshot Lock" feature
enhancement
snapshots
All issues related to the snapshots epic
triage
#972
opened Jul 30, 2024 by
ruimarinho
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
Unable to recover after specific incremental backup 20190324T054002 at Mar 24 05:40:02 2019
#926
opened May 25, 2024 by
wasiualhasib
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!
Mix and match filters to narrow down what you’re looking for.