Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1whZMO-000ItZ-17 for pgsql-announce@arkaria.postgresql.org; Wed, 08 Jul 2026 20:59:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1whZML-009QSR-38 for pgsql-announce@arkaria.postgresql.org; Wed, 08 Jul 2026 20:59:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1whZMK-009QRP-38 for pgsql-announce@lists.postgresql.org; Wed, 08 Jul 2026 20:59:09 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1whZMI-00000000DKi-3pjC for pgsql-announce@lists.postgresql.org; Wed, 08 Jul 2026 20:59:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=RoxnAP/KqWELCDibiEia3hD0hqegq/cJVsexaxs37t4=; b=aT8xJqR235tXTHLIlzUkHcLifW sF+YuvQJz8MMLTLTFoVnqmbiRz3yPEM+2p0efE+qXTnBWwnj8QpSymxNX8NJJrqA+CwXYGBrn0nWR hMYHZZs8GFTtwIdTSOQFtoGHC0ybqUJ/RwAQteBcptwTCHxG4cy8NFdm/dvzt5vCSdxZu5IlZX1W3 cCTpNCte5henIB6iXldvioySpSeoAeLAfn+394ky3/qN1znxNInT4CixrPtdFWMYdGcZd0+lcnE8H sULYlpIuc6zpaU833KXTkTkKAm/f4aXde6KxBDifNu34+BuqRWtIz0GfGYhpWGaWhHZJIr4hYTQhF ITS1z2pQ==; Received: from wrigleys.postgresql.org ([217.196.149.60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1whZMH-000jDs-2F for pgsql-announce@lists.postgresql.org; Wed, 08 Jul 2026 20:59:06 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1whZME-001lpm-1T for pgsql-announce@lists.postgresql.org; Wed, 08 Jul 2026 20:59:03 +0000 Content-Type: multipart/alternative; boundary="===============1095329811582960120==" MIME-Version: 1.0 Subject: Barman 3.19.0 and 3.19.1 Released To: PostgreSQL Announce From: EDB via PostgreSQL Announce Reply-To: david.wagoner@enterprisedb.com Date: Wed, 08 Jul 2026 20:58:53 +0000 Message-ID: <178354433320.73864.5294724179313431272@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: a1ff44e5062901a5cce39b02c72b4dc9c6c5ca30169a14ebe711b66e5986af73 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============1095329811582960120== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable We are pleased to announce the release of Barman 3.19.0 and 3.19.1, which s= hipped in quick succession on May 20 and May 26, 2026. This announcement co= vers both releases. Barman (Backup and Recovery Manager) is an open-source administration tool = for remote backups and disaster recovery of PostgreSQL servers in business-= critical environments. It relies on PostgreSQL's point-in-time recovery tec= hnology, allowing DBAs to manage a complete catalog of backups and the reco= very phase of multiple remote servers from one location. Release Highlights (3.19.0) Cloud Storage Restore Support =20 Barman can now restore backups taken with backup_method =3D local-to-cloud = or backup_method =3D postgres directly from cloud object storage, using the= standard barman restore command. A new barman cloud-wal-restore command fe= tches WAL files directly from cloud storage during recovery and supports pa= rallel fetching. This completes the cloud backup lifecycle, enabling backup= and recovery workflows entirely in the cloud. New Backup Export and Import Commands =20 New barman export-backup and barman import-backup commands let you export a= backup to a tarball for sharing or archiving, and re-register a previously= exported backup into a Barman catalog. Improvements =20 Parallel WAL archiving for barman cloud-wal-archive (--parallel flag), redu= cing WAL archival backlog during high-WAL periods. =20 Parallel WAL restore support added to barman-cloud-wal-restore. =20 Support for alternative GCP universes via the GOOGLE_CLOUD_UNIVERSE_DOMAIN = environment variable. =20 New aws_check_object_lock option checks S3 Object Lock before deleting base= backup files. =20 In-progress cloud backups are now visible in barman-cloud-backup-list rathe= r than only appearing once complete. =20 New --partial-wal flag for barman restore --no-get-wal, for opt-in inclusio= n of .partial WAL files. =20 Setuptools is no longer a runtime dependency. Bug Fixes (3.19.0) =20 Fixed backup metadata (backup.info) not being updated in cloud storage for = local-to-cloud/postgres backup methods. =20 Fixed barman restore --no-get-wal copying unusable .partial WAL files that = PostgreSQL could never apply. =20 Fixed --no-get-wal restores not copying WAL files from newer timelines on P= ostgreSQL 12+, which could cause PITR restores to fail. =20 Fixed spurious warnings about intermediary files not being removed during b= atch WAL archiving (introduced in 3.18). Bug Fixes (3.19.1) =20 Fix cloud-wal-restore failing to find compressed WAL files =20 Fixed a bug where barman-cloud-wal-restore and barman cloud-wal-restore wou= ld fail to locate a compressed WAL file when a backup file with the same pr= efix existed in the cloud storage bucket. WAL files are now correctly ident= ified even when backup files share the same prefix. Links =20 Website: https://pgbarman.org/ =20 Download: https://www.enterprisedb.com/software-downloads-postgres#barman = Documentation: https://docs.pgbarman.org/ =20 Release Notes: https://docs.pgbarman.org/release/3.19.0/releases/index.html= and https://docs.pgbarman.org/release/3.19.1/releases/index.html =20 Support: https://pgbarman.org/support/ About Barman =20 Barman is distributed under the GNU GPL 3 license and maintained by Enterpr= iseDB (EDB). --===============1095329811582960120== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Barman 3.19.0 and 3.19.1 Released
 

Barman 3.19.0 and 3.19.1 Released

We are pleased to announce the release of B= arman 3.19.0 and 3.19.1, which shipped in quick succession on May 20 and Ma= y 26, 2026. This announcement covers both releases.

Barman (Backup and Recovery Manager) is an = open-source administration tool for remote backups and disaster recovery of= PostgreSQL servers in business-critical environments. It relies on Postgre= SQL's point-in-time recovery technology, allowing DBAs to manage a complete= catalog of backups and the recovery phase of multiple remote servers from = one location.

Release Highlights (3.19.0)

Cloud Storage Restore Support
Barman can now restore backups taken with backup_method =3D local-to-cloud = or backup_method =3D postgres directly from cloud object storage, using the= standard barman restore command. A new barman cloud-wal-restore command fe= tches WAL files directly from cloud storage during recovery and supports pa= rallel fetching. This completes the cloud backup lifecycle, enabling backup= and recovery workflows entirely in the cloud.

New Backup Export and Import Commands
New barman export-backup and barman import-backup commands let you export a= backup to a tarball for sharing or archiving, and re-register a previously= exported backup into a Barman catalog.

Improvements
Parallel WAL archiving for barman cloud-wal-archive (--parallel flag), redu= cing WAL archival backlog during high-WAL periods.
Parallel WAL restore support added to barman-cloud-wal-restore.
Support for alternative GCP universes via the GOOGLE_CLOUD_UNIVERSE_DOMAIN = environment variable.
New aws_check_object_lock option checks S3 Object Lock before deleting base= backup files.
In-progress cloud backups are now visible in barman-cloud-backup-list rathe= r than only appearing once complete.
New --partial-wal flag for barman restore --no-get-wal, for opt-in inclusio= n of .partial WAL files.
Setuptools is no longer a runtime dependency.

Bug Fixes (3.19.0)
Fixed backup metadata (backup.info) not being updated in cloud storage for = local-to-cloud/postgres backup methods.
Fixed barman restore --no-get-wal copying unusable .partial WAL files that = PostgreSQL could never apply.
Fixed --no-get-wal restores not copying WAL files from newer timelines on P= ostgreSQL 12+, which could cause PITR restores to fail.
Fixed spurious warnings about intermediary files not being removed during b= atch WAL archiving (introduced in 3.18).

Bug Fixes (3.19.1)
Fix cloud-wal-restore failing to find compressed WAL files
Fixed a bug where barman-cloud-wal-restore and barman cloud-wal-restore wou= ld fail to locate a compressed WAL file when a backup file with the same pr= efix existed in the cloud storage bucket. WAL files are now correctly ident= ified even when backup files share the same prefix.

Links
Website: https://pgbarman.org/
Download: https://www.enterprisedb.com/software-downloads-postgres#barman Documentation: https://docs.pgbarman.org/
Release Notes: https://docs.pgbarman.org/release/3.19.0/releases/index.html= and https://docs.pgbarman.org/release/3.19.1/releases/index.html
Support: https://pgbarman.org/support/

About Barman
Barman is distributed under the GNU GPL 3 license and maintained by Enterpr= iseDB (EDB).

This email was sent to you from EDB. It was delivered on their behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to EDB.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Open Source. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============1095329811582960120==--