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 1sea6L-00917B-Vb for pgsql-announce@arkaria.postgresql.org; Thu, 15 Aug 2024 13:01:14 +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 1sea6K-00GCLJ-Ky for pgsql-announce@arkaria.postgresql.org; Thu, 15 Aug 2024 13:01:12 +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.94.2) (envelope-from ) id 1sea6J-00GCL2-Kz for pgsql-announce@lists.postgresql.org; Thu, 15 Aug 2024 13:01:11 +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.94.2) (envelope-from ) id 1sea6E-004rbe-F8 for pgsql-announce@lists.postgresql.org; Thu, 15 Aug 2024 13:01:10 +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=ovN7nQQQYB3YDrpdh018Pejo1xYw/w/95cT3cHld7no=; b=KUSKjtijDtZcmchIrOEgK4M2ap pAwHQVyzhqqBNsU5KspFUb6u8GKWynR/uTP90O/DM+DsyVOUBUdy9MPB9MJBg8N/V6DBeUUKEYeTO evicHG/R7dU2lfhWvc407gSgLokmyFf4JbLPkov2TH6uQgNbaYNHNKDFW3FwTOlJjhSD21juh7h0w ITevh95uQ1sSy0mZBI2n8SAWLycpMobfTXx5RZiCTcPvI7JsUegZ+ZfYyytbIQ2cUUljaDMrDAu9+ MgMUhhvT6ZGQcu3D1CQ52yZa2JOc6iFNJVVoZr4073Wi2GuEApkHYZtCGheIjG0vitz3pyF8py1lP jGYzcJAg==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sea6D-00F93K-Bj for pgsql-announce@lists.postgresql.org; Thu, 15 Aug 2024 13:01:05 +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 1sea6A-007qxi-SC for pgsql-announce@lists.postgresql.org; Thu, 15 Aug 2024 13:01:03 +0000 Content-Type: multipart/mixed; boundary="===============1118720364825548653==" MIME-Version: 1.0 Subject: WAL-G 3.0.3 released To: PostgreSQL Announce From: WAL-G via PostgreSQL Announce Reply-To: x4mmm@yandex-team.ru Date: Thu, 15 Aug 2024 13:00:55 +0000 Message-ID: <172372685577.395942.8659652103574561700@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 0e7553fcc60e84ea87d91971154022d319ff9da45ac672d12972f4f6d180a4e8 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============1118720364825548653== Content-Type: multipart/alternative; boundary="===============1496479644413946943==" MIME-Version: 1.0 --===============1496479644413946943== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable WAL-G team is happy to announce the release of WAL-G 3.0.3 WAL-G is a tool for archival database restoration for PostgreSQL, Greenplum= DB, MySQL/MariaDB, MongoDB, etcd and several other databases. Major feature of this release is full support for OrioleDB. WAL-G supported block-level incremental backups since [v0.1.3](https://gith= ub.com/wal-g/wal-g/releases/tag/v0.1.3), but it previously treated OrioleDB= data as a collection of unknown files. Now WAL-G understands if OrioleDB i= s installed into cluster and makes efficient backup copies of OrioleDB data= . Thanks to Supabase engineers for working on WAL-G. Additionally, this release includes two new commands for Postgres: ```catch= up-send``` and ```catchup-receive```. These commands are useful when you ne= ed to bring a lagging replica up to date without pushing a new backup to th= e storage. In essence, they work like pg_rewind but in reverse. Perhaps we = should rename them to pg_wind. This release also mitigates several CVEs in dependencies ([CVE-2023-39325](= https://github.com/wal-g/wal-g/pull/1675), [GHSA-9763-4f94-gfch](https://gi= thub.com/wal-g/wal-g/pull/1715)) and fixes assorted bugs. WAL-G v3.0.3 is available for download on our [GitHub releases page](https:= //github.com/wal-g/wal-g/releases). Have a nice day! --===============1496479644413946943== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable WAL-G 3.0.3 released
 

WAL-G 3.0.3 released

WAL-G team is happy to announce the release= of WAL-G 3.0.3

WAL-G is a tool for archival database resto= ration for PostgreSQL, GreenplumDB, MySQL/MariaDB, MongoDB, etcd and severa= l other databases.

Major feature of this release is full suppo= rt for OrioleDB. WAL-G supported block-level incremental backups since v0.1.3, but it previously treated OrioleDB data as = a collection of unknown files. Now WAL-G understands if OrioleDB is install= ed into cluster and makes efficient backup copies of OrioleDB data. Thanks = to Supabase engineers for working on WAL-G.

Additionally, this release includes two new= commands for Postgres: catchup-send and catchup-receive= . These commands are useful when you need to bring a lagging replica= up to date without pushing a new backup to the storage. In essence, they w= ork like pg_rewind but in reverse. Perhaps we should rename them to pg_wind= .

This release also mitigates several CVEs in= dependencies (CVE-2023-39325, GHSA-9763-4f94-gfch) and fixes assorted bugs.

WAL-G v3.0.3 is available for download on o= ur GitHub releases page.

Have a nice day!
This email was sent to you from WAL-G. It was delivered on their behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to WAL-G.

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/.
 
--===============1496479644413946943==-- --===============1118720364825548653==--