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 1wPWhI-000nDI-06 for pgsql-announce@arkaria.postgresql.org; Wed, 20 May 2026 02:30: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 1wPWhF-005ey3-3B for pgsql-announce@arkaria.postgresql.org; Wed, 20 May 2026 02:30: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 1wPWhE-005exl-3A for pgsql-announce@lists.postgresql.org; Wed, 20 May 2026 02:30:10 +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 1wPWhC-00000000PzY-0Ttf for pgsql-announce@lists.postgresql.org; Wed, 20 May 2026 02:30: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=VKy6eI2Q2eaV+tEs05PfO0Go6+mnvNG5BaDoLsIfOP8=; b=kVT4L9IXRz39xvKqSY5Wm4P7oL 18SLzYqlmeWOfCroIrkBAHQ37JlrXxhxeXAutqeR5txg6Xu4b9o49sdhN9L0a0NlSILsYksIkUHEW WsMHUuFxlRiSXRJW//LaJeMZeox/zSUmfX7OoKF+e4EBZz9FnWHr/C5BUV7M1CHp4yy3mUE9zzFyR bvtDgTLsImIgX3JYk+eNxG8j3hBbUlmaxK8uA47aAHBNwKILVYGXshlbwp/KghFy84e8I2RegOMVT 10AHL8EGpG0Zc2ClccrLC7sf5QOP976ygdDtkkfB6wMlOUwFvFKlTUXqEWVuw2xC5qFfS/JHJbLmL fEPIWnXg==; 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 1wPWhB-001G0o-0o for pgsql-announce@lists.postgresql.org; Wed, 20 May 2026 02:30: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 1wPWhA-002Vyw-1t for pgsql-announce@lists.postgresql.org; Wed, 20 May 2026 02:30:04 +0000 Content-Type: multipart/alternative; boundary="===============9186168809379983426==" MIME-Version: 1.0 Subject: Barman 3.18.0 Released To: PostgreSQL Announce From: EDB via PostgreSQL Announce Reply-To: david.wagoner@enterprisedb.com Date: Wed, 20 May 2026 02:29:51 +0000 Message-ID: <177924419171.802.7262240429295511778@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 0e3b07a906aa306a038685d4d931ec2f464cb4d3f084055b4d96ea732a290469 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============9186168809379983426== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Barman 3.18.0 Released =20 Date: 2026-03-12 =20 From: EnterpriseDB We are pleased to announce the release of Barman 3.18.0. 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. This release marks a significant step toward a unified cloud backup experie= nce, introducing incremental backups for cloud storage and bringing cloud b= ackup operations directly into the main Barman CLI. Release Highlights Incremental Backups for Cloud Storage (Experimental) Barman 3.18 introduces block-level incremental backups for cloud storage, r= educing storage costs and upload times by sending only changed data blocks.= Built on native PostgreSQL streaming backups via pg_basebackup, this featu= re streams directly to cloud storage (S3, Azure Blob, GCS) through a small = configurable local staging area, with no full backup copy stored on the Bar= man host. Configurable via the new cloud_staging_directory and cloud_stagin= g_max_size options. Note: restore support is not yet available in this rele= ase and will be added in a future release. New local-to-cloud Backup Method A new backup_method =3D local-to-cloud option enables direct cloud backup t= hrough the main barman CLI, without the standalone barman-cloud-* scripts. = This is the first step toward unifying and eventually deprecating those scr= ipts. Cloud storage is configured directly in the Barman config using a clo= ud URL in basebackups_directory (e.g., s3://bucket/path). New barman cloud-wal-archive Command Complements local-to-cloud by enabling WAL archiving directly from PostgreS= QL's pg_wal directory to cloud object storage. Supports in-memory compressi= on (gzip, bzip2, xz, snappy, zstd, lz4) before upload. Improvements LZ4 Compression for Cloud Backups: barman-cloud-backup now supports --lz4 c= ompression, joining --gzip, --bzip2, and --snappy as cloud compression opti= ons. S3 Addressing Style Control: A new --addressing-style option (auto, virtual= , or path) improves compatibility with S3-compatible storage systems requir= ing virtual-hosted-style addressing. Custom Restore Command: barman recover now accepts a --restore-command opti= on to override the default WAL restore command at recovery time, without ne= eding to manually edit PostgreSQL configuration files afterward. Python 3.14 Compatibility: Cloud backup operations now work correctly with = Python 3.14. Bug Fixes WAL Archiving File Handle Leak: Fixed a resource leak in cloud WAL archivin= g where file handles were not properly closed after upload, which could cau= se "Too many open files" errors on long-running archiving services. 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.18.0/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). --===============9186168809379983426== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Barman 3.18.0 Released
 

Barman 3.18.0 Released

Subject: Barman 3.18.0 Released
Date: 2026-03-12
From: EnterpriseDB

We are pleased to announce the release of B= arman 3.18.0.

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.

This release marks a significant step towar= d a unified cloud backup experience, introducing incremental backups for cl= oud storage and bringing cloud backup operations directly into the main Bar= man CLI.

Release Highlights

Incremental Backups for Cloud Storage (Expe= rimental) Barman 3.18 introduces block-level incremental backups for cloud storage, r= educing storage costs and upload times by sending only changed data blocks.= Built on native PostgreSQL streaming backups via pg_basebackup, this featu= re streams directly to cloud storage (S3, Azure Blob, GCS) through a small = configurable local staging area, with no full backup copy stored on the Bar= man host. Configurable via the new cloud_staging_directory and cloud_stagin= g_max_size options. Note: restore support is not yet available in this rele= ase and will be added in a future release.

New local-to-cloud Backup Method A new backup_method =3D local-to-cloud option enables direct cloud backup t= hrough the main barman CLI, without the standalone barman-cloud-* scripts. = This is the first step toward unifying and eventually deprecating those scr= ipts. Cloud storage is configured directly in the Barman config using a clo= ud URL in basebackups_directory (e.g., s3://bucket/path).

New barman cloud-wal-archive Command Complements local-to-cloud by enabling WAL archiving directly from PostgreS= QL's pg_wal directory to cloud object storage. Supports in-memory compressi= on (gzip, bzip2, xz, snappy, zstd, lz4) before upload.

Improvements

LZ4 Compression for Cloud Backups: barman-c= loud-backup now supports --lz4 compression, joining --gzip, --bzip2, and --= snappy as cloud compression options.

S3 Addressing Style Control: A new --addres= sing-style option (auto, virtual, or path) improves compatibility with S3-c= ompatible storage systems requiring virtual-hosted-style addressing.

Custom Restore Command: barman recover now = accepts a --restore-command option to override the default WAL restore comm= and at recovery time, without needing to manually edit PostgreSQL configura= tion files afterward.

Python 3.14 Compatibility: Cloud backup ope= rations now work correctly with Python 3.14.

Bug Fixes

WAL Archiving File Handle Leak: Fixed a res= ource leak in cloud WAL archiving where file handles were not properly clos= ed after upload, which could cause "Too many open files" errors on long-run= ning archiving services.

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.18.0/releases/index.html Support: https://pgbarman.org/support/

About Barman

Barman is distributed under the GNU GPL 3 l= icense and maintained by EnterpriseDB (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/.
 
--===============9186168809379983426==--