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 1s93AW-00H0PE-9x for pgsql-announce@arkaria.postgresql.org; Mon, 20 May 2024 13:35: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 1s93AV-001sBZ-1c for pgsql-announce@arkaria.postgresql.org; Mon, 20 May 2024 13:35:11 +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 1s93AT-001sAd-Vj for pgsql-announce@lists.postgresql.org; Mon, 20 May 2024 13:35: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.94.2) (envelope-from ) id 1s93AQ-0017tg-2V for pgsql-announce@lists.postgresql.org; Mon, 20 May 2024 13:35: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=YAdWq0LUmlB0VZlGoAil0p5atj1xKnIHwcc1LtUTI0g=; b=Wac4o25QRGy9j3IRpYz9AosVCq a8gNGPkOvZs/8FfeAc/kg/mINudE61StR3imqoO0shswzj2iBvoa6JbjdYEg4jsLoU66ZpA9l820g N2LVFuoGkCey/C/YWDkZVruIUjYrDgN55nPphW9A0KHIytzbl8wi2ntZpmprlz6kAQBltQ+qvoiKe 7CMJw1fq+JzG/ciGPte+ZAvz0DRNe+JGYTgwMIF4IwbbfrBQ2ORPimZIUoE6ACu/+l5jdcf/wlHnU eq4he/8B6TY0vPuhFtKBpUrDgNu1bZpeq2VpOLGX/X7o0iC2GVtgMxdLv9UvWIbDSxw+klQ1MgYGq I5jhio4w==; 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 1s93AO-003aLT-9p for pgsql-announce@lists.postgresql.org; Mon, 20 May 2024 13:35: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 1s93AM-0061kv-5R for pgsql-announce@lists.postgresql.org; Mon, 20 May 2024 13:35:02 +0000 Content-Type: multipart/mixed; boundary="===============8132008058152820815==" MIME-Version: 1.0 Subject: pg_dumpbinary v2.17 released To: PostgreSQL Announce From: Gilles Darold via PostgreSQL Announce Reply-To: gilles@darold.net Date: Mon, 20 May 2024 13:34:40 +0000 Message-ID: <171621208007.685.13412455324113040038@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 3e82a1b9fc1b2f01adaba9788fe0582b21a723cbc78f6301396bbc50ab099e10 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============8132008058152820815== Content-Type: multipart/alternative; boundary="===============7905009431125657687==" MIME-Version: 1.0 --===============7905009431125657687== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable **Grenoble, France - Mai 20, 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. This release adds two new options to command pg_restorebinary: * Add option `-C, --create` to pg_restorebinary to create the database before restoring into it. Like with pg_restore you must provide a database to connect using the `-d` option. * Add `--dump-create` to print to stdout the create and alter database statements. `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) --===============7905009431125657687== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pg_dumpbinary v2.17 released
 

pg_dumpbinary v2.17 released

Grenoble, France - Mai 20, 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.

This release adds two new options to comman= d pg_restorebinary:

  • Add option -C, --create to pg_restorebinary to create the database before restoring into it. Like with pg_restore you must provide a database to connect using the -d option.
  • Add --dum= p-create to print to stdout the create and alter database statements.

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 los= s.
  • 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/.
 
--===============7905009431125657687==-- --===============8132008058152820815==--