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.94.2) (envelope-from ) id 1rU65S-008puP-QN for pgsql-announce@arkaria.postgresql.org; Sun, 28 Jan 2024 14:24:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rU65R-009BEt-Rq for pgsql-announce@arkaria.postgresql.org; Sun, 28 Jan 2024 14:24:41 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rU618-008n6z-Ma for pgsql-announce@lists.postgresql.org; Sun, 28 Jan 2024 14:20:14 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rU610-004A8q-Bx for pgsql-announce@lists.postgresql.org; Sun, 28 Jan 2024 14:20:14 +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=9q5oeeO0TNZJoGTi50WGs7qlzLEVAxsmLsre5bfNG28=; b=fPkdtg4v236KAj/6uGvVGo26c9 oDWfACu6o1UJVoN7nzs+QXGb9PwvgGqvL5alTa+tIWNdMOpmEaGevLk/uKEczJhpRr7raqUp2vlaj 8G4LlhH+/yqFDqwFbktlNNL9yD2D4T4KUlYBTYTfe58HCMicNkm9iefnCoDBCsGz/ACLdUmevA4vt 8hLuPt0lcutYENuTdTGWh2ExodFVXeZ4Nz7gBMAGXHPa8K3othfISRDfiDTKSiRugjKhTAZPAPBeV 1aKRTZDIA6FrzbHl/4mpYI5rJ2pVqsqGsUEh66PzKMvLXH+/XdmgwXJEvI/3tOBIVXppKWpDQhnnu 2sxUaobQ==; Received: from wrigleys.postgresql.org ([87.238.57.234]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rU60y-00BXw8-JE for pgsql-announce@lists.postgresql.org; Sun, 28 Jan 2024 14:20:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rU60w-0091te-4p for pgsql-announce@lists.postgresql.org; Sun, 28 Jan 2024 14:20:02 +0000 Content-Type: multipart/mixed; boundary="===============3740547744287457586==" MIME-Version: 1.0 Subject: Barman 3.10.0 Released To: PostgreSQL Announce From: EDB via PostgreSQL Announce Reply-To: adam.wright@enterprisedb.com Date: Sun, 28 Jan 2024 14:19:20 +0000 Message-ID: <170645156059.665.7784364356884442697@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 9a8fffbc351119119b37d9c036558712f08a8370eb17910063baa2599c8a57ad List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============3740547744287457586== Content-Type: multipart/alternative; boundary="===============0199244337454732727==" MIME-Version: 1.0 --===============0199244337454732727== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [EDB](https://www.enterprisedb.com) is pleased to announce the release of B= arman 3.10.0.=20 ## Highlights of this release: ### Features:=20 * Limit the average bandwidth used by `barman-cloud-backup` when backing up to either AWS S3 or Azure Blob Storage according to the value set by a new CLI option `--max-bandwidth`. * Add the new configuration option `lock_directory_cleanup` That enables cron to automatically clean up the barman_lock_directory from unused lock files. * Add support for a new type of configuration called `model`. The model acts as a set of overrides for configuration options for a given Barman server. * Add a new barman command `barman config-update` that allows the creation and the update of configurations using JSON * Related to this Barman release, [pg_backup_api](https://github.com/Enterp= riseDB/barman/blob/master/NEWS) has been updated and released to support th= ese new features. As a result, Barman now supports changes in the configur= ation whilst it's running. This pg-backup-api release adds the required end= points to trigger that switch when requested. ### Bug fixes: * Fix a bug that caused `--min-chunk-size` to be ignored when using `barman= -cloud-backup` as a hook script in Barman. This information is also published in the [NEWS](https://github.com/Enterpr= iseDB/barman/blob/master/NEWS) for Barman. ### About Barman Backup and Recovery Manager (or Barman) is an open-source administration to= ol for remote backups and disaster recovery of PostgreSQL servers in busine= ss-critical environments. It relies on PostgreSQL=E2=80=99s robust and reli= able Point-In-Time Recovery technology, allowing DBAs to remotely manage a = complete catalog of backups and the recovery phase of multiple remote serve= rs =E2=80=93 all from one location. Barman is distributed under GNU GPL 3 a= nd maintained by [EDB](https://www.enterprisedb.com). --===============0199244337454732727== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Barman 3.10.0 Released
 

Barman 3.10.0 Released

EDB is pleased to an= nounce the release of Barman 3.10.0.

Highlights of this release:

Features:

  • Limit the avera= ge bandwidth used by barman-cloud-backup when backing up to either AWS S3 or Azure Blob Storage according to the value set by a new CLI option --max-bandwidth.
  • Add the new con= figuration option lock_directory_cleanup That enables cron to automatically clean up the barman_lock_directory from unused lock files.
  • Add support for= a new type of configuration called model. The model acts as a set of overrides for configuration options for a given Barman server.
  • Add a new barma= n command barman config-update that allows the creation and the update of configurations using JSON
  • Related to this= Barman release, pg_backup_ap= i has been updated and released to support these new features. As a re= sult, Barman now supports changes in the configuration whilst it's running.= This pg-backup-api release adds the required endpoints to trigger that swi= tch when requested.

Bug fixes:

  • Fix a bug that = caused --min-chunk-size to be ignored when using barman-= cloud-backup as a hook script in Barman.

This information is also published in the <= a href=3D"https://github.com/EnterpriseDB/barman/blob/master/NEWS" style=3D= "color: #3498db; text-decoration: underline">NEWS for Barman.

About Barman

Backup and Recovery Manager (or Barman) is = an open-source administration tool for remote backups and disaster recovery= of PostgreSQL servers in business-critical environments. It relies on Post= greSQL=E2=80=99s robust and reliable Point-In-Time Recovery technology, all= owing DBAs to remotely manage a complete catalog of backups and the recover= y phase of multiple remote servers =E2=80=93 all from one location. Barman = is distributed under GNU GPL 3 and maintained by 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/.
 
--===============0199244337454732727==-- --===============3740547744287457586==--