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 1u2NlK-00HJ1H-Qb for pgsql-announce@arkaria.postgresql.org; Wed, 09 Apr 2025 05:14:11 +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 1u2NlJ-000HTM-9a for pgsql-announce@arkaria.postgresql.org; Wed, 09 Apr 2025 05:14:09 +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 1u2NlI-000HST-8C for pgsql-announce@lists.postgresql.org; Wed, 09 Apr 2025 05:14:08 +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.96) (envelope-from ) id 1u2NlG-003oM3-1i for pgsql-announce@lists.postgresql.org; Wed, 09 Apr 2025 05:14:07 +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=dwreCBQCB96U2JOW8SKO4HdCA9pkjK9fpqXna8nJXHg=; b=pEWI8Yxn8FjWO3P5VbeiWf4Jry MEzYMRMuj7MHJqynPdgcroKLaMAkfTe6fGzpTFP3Nrn8Mts8JAP53qh6JXVJtcD+rwkTxEHVliizl CG79siWJFjPcZer0n0H6PiWLrI3hDs2+aK5Ay2lwm16oRiqoepffY7clQlwdmt3hXduCaRoxFg2D7 64wcC1KUk5xw9cRbg16d8gc/gfACRRsIx/EasVUfZSFX3nkEQikHs1fQdjzQczSFKxApfVOs15Ssf w1VupuYoyA33ZC8SlOzjhmd4eIHYzeR1rKzJqMLsvbN2daUgOL+BXqXZTPs6s2M8e8SMLEiGOVKnY bthBVsPg==; 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 1u2NlE-002J4L-Hf for pgsql-announce@lists.postgresql.org; Wed, 09 Apr 2025 05:14: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 1u2NlD-003eB7-8h for pgsql-announce@lists.postgresql.org; Wed, 09 Apr 2025 05:14:03 +0000 Content-Type: multipart/mixed; boundary="===============3755934358940867916==" MIME-Version: 1.0 Subject: pg_dumpbinary v2.19 released To: PostgreSQL Announce From: Gilles Darold via PostgreSQL Announce Reply-To: gilles@darold.net Date: Wed, 09 Apr 2025 05:13:23 +0000 Message-ID: <174417560395.677.6850321635364060756@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 9fb62d4c4286c3c2bd27b00c999461d3c0a515d0d7fcf20d9193e9f3547bdb1b List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============3755934358940867916== Content-Type: multipart/alternative; boundary="===============6397477167207943036==" MIME-Version: 1.0 --===============6397477167207943036== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable **Antananarivo, Madagascar - April 08, 2025** ## 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 is a maintenance release that fixes a major bug when dumping data from= tables with the dollar sign in their name or namespace. - Set `application_name` to program name when connecting to PostgreSQL. - Fix missing data when dumping a table with the dollar sign in its name or the schema name. `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) --===============6397477167207943036== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pg_dumpbinary v2.19 released
 

pg_dumpbinary v2.19 released

Antananarivo, Madagascar - April 08= , 2025

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 is a maintenance release that fixes a = major bug when dumping data from tables with the dollar sign in their name or namespace.

  • Set appli= cation_name to program name when connecting to PostgreSQL.
  • Fix missing dat= a when dumping a table with the dollar sign in its name or the schema name.

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/.
 
--===============6397477167207943036==-- --===============3755934358940867916==--