Activity for Marco Nenciarini
-
Marco Nenciarini committed [8b31a2]
Release notes for 2.12
-
Version set to 2.12
-
New `backup_method` option: `local-rsync`
-
Update the ChangeLog file
-
Avoid any attempt to connect to PostgreSQL during tests
-
Version set to 2.11
-
Add missing files in scripts/set-version.sh
-
Release notes for 2.11
-
Add Python 3.8 compatibility to release metadata
-
Update the ChangeLog file
-
Pin isort version < 5.0 because it currently breaks flake8-isort
-
Fix typos
-
Gracefully handle KeyboardInterrupt in barman-cloud-restore
-
Document `barman-cli-cloud` installation
-
Add --log-level option to override the global configuration
-
Run flake8 on python3.7
-
Add support for pre-release versions in PostgreSQLClient wrapper
-
Add testing on Python 3.8
-
[Errno 13] Permission denied: ...../xlog.db' with cifs share
-
Clesed with commit [6f3874]
-
Collect `wal_keep_segments` in server status
-
Improve logging of replication slots and restore points
-
Ensure that begin_wal is valorised before acting on it
-
Fix cosmetic issue detected by flake8
-
Add support for `--endpoint-url` option to cloud utilities
-
Detect PostgreSQL devel versions (i.e. 13devel)
-
S3 WAL restore gets .partial files and skips backup files
-
Require boto3 < 1.11 when testing with Python 2.6
-
Backup fails due to encoding error / solution inside
-
The issue has been fixed in several commits that improved the handling of decoding errors. Please consider that the workaround proposed, that may work in some cases, isn ugly hack that breacks several assumptions in the python interpreter and may introduce more errors. If you find any decoded error, please report it, so we can update the barman code to be resilient to encoding errors.
-
postgres@postgres ERROR: function pg_last_xlog_receive_location() does not exist at character 26
-
These queries are not from barman source code. I suppose they are coming from another tool that is trying to monitor your standby lag.
-
Suppress messages and warning with SSH connections in barman-cli
-
Do not require ListBuckets permission to use barman-cloud
-
Add verbose logging to barman-cloud-wal-archive
-
Avoid connecting to PostgreSQL while reading a backup.info file
-
"Error: xx is already present in server xx. File moved to errors directory"
-
Hi, what you see means that at the some time in the past, your postgres server restarted the wal sequence. That usually happen when you use pg_upgrade or you replace your cluster in another way without changing the name of the server in barman. After some time you reach the old WAL name and therefore the error you see. The version 2.10 of barman (it will be officially out on 5 December 2019) has a new mechanism to prevent this kind of issues. It introduces verification of the PostgreSQL instance's...
-
Manage KeyboardInterrupt exception in barman-cloud-backup
-
Add documentation section about `barman-cli`
-
Fix circular import error importing barman.compression
-
Removed broken link on standby settings
-
Make sure to remove temporary files during unit tests
-
Minor clarification to "backup_options" description
-
Fix WAL file name validation in barman-cloud-walarchive
-
Add man pages for cloud utilities to setup.py
-
Add disclaimer for experimental support for cloud utilities
-
Add sphinx to isort configuration
-
Display a warning for WAITING_FOR_WALS backups
-
Improve `receive-wal --reset` command
-
Version set to 2.10
-
Verify the PostgreSQL system identifier
-
Remove race condition on cloud upload completion
-
Implement statistics during cloud-backup upload
-
Small change in log file for `get-wal` command
-
Parallel barman-cloud-backup upload
-
Improve error in cloud clients when boto3 is missing
-
Remove recovery documentation link from documentation
-
Fix issue with list-server and empty description
-
Update the ChangeLog file
-
Update set-version.sh script with the new doc files
-
Small improvements in cloud utilities documentation
-
Use the same WAL directory structure in S3
-
Fix exception with server side encryption
-
Add WAL file name validation in barman-cloud-walarchive
-
Enable python3 for bash completion
-
Use CloudInterface class in cloud_wal_archive
-
Add note about PostgreSQL upgrades
-
Minor fixes in WAL delete hook scripts
-
Log formatting tweak for consistency
-
Version set to 2.9
-
Add release notes for version 2.9
-
Update the ChangeLog file
-
Skip WAL archive failure if we have a terminated backup
-
Add '--bwlimit' option to backup and recover commands
-
barman-wal-restore: Add --spool-dir option
-
Clarify some options in passive node configuration example
-
Use latest PostgreSQL release in sample configurations
-
replication-status doesn't show streamers without a slot
-
Updated requirements section in the documentation
-
Version set to 2.8
-
Update NEWS file for release 2.8
-
Cosmetic changes in default barman.conf
-
Improve documentation on backup from standby
-
Update the ChangeLog file
-
Update Sphinx docuemntation build environment
-
Fix exclude_and_protect_filter
-
Remove spurious message when resetting WAL
-
Fix encoding error in get-wal on Python 3
-
Add Python 3.7 to unit tests
-
Drop Python 3.4 support. Add Python 3.7 to test suite
-
Drop Python 3.4 support. Add Python 3.7 to test suite
-
Support psycopg2 2.8 in unit tests
-
Collect more PostgreSQL settings during get_remote_status()
-
Drop Python 3.4 support. Add Python 3.7 to test suite
-
Version set to 2.8a1
-
Remove obsolete rpp packagin files
-
Version set to 2.7
-
Add utility script to set a new barman version
-
Update NEWS file for release 2.7
1 >
