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 1rNvvn-00HCuc-PQ for pgsql-announce@arkaria.postgresql.org; Thu, 11 Jan 2024 14:21:16 +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 1rNvvn-00BoQX-0L for pgsql-announce@arkaria.postgresql.org; Thu, 11 Jan 2024 14:21:15 +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 1rNvvm-00BoQ3-4x for pgsql-announce@lists.postgresql.org; Thu, 11 Jan 2024 14:21: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 1rNvvf-0011RC-Kg for pgsql-announce@lists.postgresql.org; Thu, 11 Jan 2024 14:21:13 +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=VL5OWTtXL3PqSI2tWPYCXIWTs4GI5w8ni8i5J71fzg4=; b=i+/6BmdwJU4dZvFdBVmel0XK4I IlsxQdlbtZCE3HChAle+IRqNxarfhc/4YjRdz49UW8Nqa++4ygmvFhPwOaNQ8aTZC8bz25QLhTUE+ 93UvjGxKJvG4lpxgTISth4DBJbcZfotPskc/qmwx389QwCn0acJQApQWDHgXNlTygs1qiqMZ2a/go aPkLAjzEQK1gNsCnEEF/t2rUvRqbhhfvEMHd0st0Tj14Mfv2Qy709kcOEeUunH9ZkZ4gxifFbe/JT ko7dZuEfNxhBliKNbWmIfGsasvEWSUNQaCHS0gWILFcuj+HEgk7o6rUOyj5m3C/irJHNUT+pJ6hj8 Vd/Y8Fow==; Received: from wrigleys.postgresql.org ([2a02:c0:301:0:ffff::34]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rNvvc-0033Dv-GS for pgsql-announce@lists.postgresql.org; Thu, 11 Jan 2024 14:21:06 +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 1rNvva-006ig9-U5 for pgsql-announce@lists.postgresql.org; Thu, 11 Jan 2024 14:21:03 +0000 Content-Type: multipart/mixed; boundary="===============3021957729909287255==" MIME-Version: 1.0 Subject: pg_dumpbinary v2.14 released To: PostgreSQL Announce From: Gilles Darold via PostgreSQL Announce Reply-To: gilles@darold.net Date: Thu, 11 Jan 2024 14:20:36 +0000 Message-ID: <170498283693.662.2561052471193287492@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: ff9da9dbf60db5da9ec2122ee9789b05405703966b1bd803f46c6d4540e56da4 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============3021957729909287255== Content-Type: multipart/alternative; boundary="===============0192134151612994785==" MIME-Version: 1.0 --===============0192134151612994785== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable **Zurich, Switzerland - January 10th, 2024** ## pg_dumpbinary `pg_dumpbinary` dumps a PostgreSQL database to a binary format. The resulti= ng dump must be restored using `pg_restorebinary`, which is provided. pg_dumpbinary 2.14 was released today, it adds two new options and fixes so= me bugs reported by users since last release. - Add new option `--with-child`, when `-t` or `-T` options are used, to inc= lude or exclude child and partition tables. pg_dump will be used instead wi= th options `--table-and-children` or `--exclude-table-and-children`. It req= uires PostgreSQL >=3D 16. - Add `-V, --verbose` option that lists tables included in the dump. - Add `-A, --attach SNAPSHOT` to be able to attach pg_dumpbinary to an exis= ting snapshot instead of creating a dedicated one. - Fix dump failure when sequences name have spaces. A full list of changes and acknowledgments can be found [here](https://gith= ub.com/lzlabs/pg_dumpbinary/releases/tag/v2.14) `pg_dumpbinary` is useful when: * You have bytea that can not be exported by `pg_dump` because the total size of the escape/hex output exceeds 1Gb. * You have custom type that stores `\0` internally in bytea but data are exported by pg_dump as char/varchar/text. In this case pg_dump truncates all data after the first '\0', resulting in data loss. * Other cases where a binary output format is useful. In these kinds of cases `pg_dumpbinary` helps by dumping the PostgreSQL database in a binary format. In all other cases the pg_dump/pg_restore commands distributed with PostgreSQL are preferred. See the documentation for a more complete description of available features. ## Links & Credits pg_dumpbinary is an Open Source project from [LzLabs GmbH](https://www.lzla= bs.com/). Contributions and ideas are welcome. Send your ideas, features requests, or patches using GitHub's tool= s. Links : * Documentation: [https://github.com/lzlabs/pg_dumpbinary/blob/master/READM= E.md](https://github.com/lzlabs/pg_dumpbinary/blob/master/README.md) * Download: [https://github.com/lzlabs/pg_dumpbinary/releases/](https://gi= thub.com/lzlabs/pg_dumpbinary/releases/) * Support: use GitHub report tool at [https://github.com/lzlabs/pg_dumpbina= ry/pg_dumpbinary/issues](https://github.com/lzlabs/pg_dumpbinary/pg_dumpbin= ary/issues) --===============0192134151612994785== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pg_dumpbinary v2.14 released
 

pg_dumpbinary v2.14 released

Zurich, Switzerland - January 10th,= 2024

pg_dumpbinary

pg_dumpbinary dumps a PostgreS= QL database to a binary format. The resulting dump must be restored using pg_restorebinary, which is provided.

pg_dumpbinary 2.14 was released today, it a= dds two new options and fixes some bugs reported by users since last releas= e.

  • Add new option = --with-child, when -t or -T options = are used, to include or exclude child and partition tables. pg_dump will be= used instead with options --table-and-children or --exc= lude-table-and-children. It requires PostgreSQL >=3D 16.
  • Add -V, -= -verbose option that lists tables included in the dump.
  • Add -A, -= -attach SNAPSHOT to be able to attach pg_dumpbinary to an existing s= napshot instead of creating a dedicated one.
  • Fix dump failur= e when sequences name have spaces.

A full list of changes and acknowledgments = can be found here

pg_dumpbinary is useful when:<= /p>

  • You have bytea = that can not be exported by pg_dump because the total size of the escape/hex output exceeds 1Gb.
  • You have custom= type that stores \0 internally in bytea but data are exported by pg_dump as char/varchar/text. In this case pg_dump truncates all data after the first '\0', resulting in data loss.
  • Other cases whe= re a binary output format is useful.

In these kinds of cases pg_dumpbinary= helps by dumping the PostgreSQL database in a binary format. In all other cases the pg_dump/pg_restore commands distributed with PostgreSQL are preferred.

See the documentation for a more complete d= escription of available features.

Links & Credits

pg_dumpbinary is an Open Source project fro= m LzLabs GmbH. Contributions and ideas are welcome. Send your ideas, features requests, or patches using GitHub's tool= s.

Links :
This email was sent to you from Gilles Darold. It was delivered on their be= half by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to Gilles Darold.

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/.
 
--===============0192134151612994785==-- --===============3021957729909287255==--