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 1rtElg-00DMqD-Lq for pgsql-announce@arkaria.postgresql.org; Sat, 06 Apr 2024 22:44:13 +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 1rtElf-0003LL-QH for pgsql-announce@arkaria.postgresql.org; Sat, 06 Apr 2024 22:44:11 +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 1rtEle-0003Kx-VA for pgsql-announce@lists.postgresql.org; Sat, 06 Apr 2024 22:44:11 +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 1rtElb-001AmE-4w for pgsql-announce@lists.postgresql.org; Sat, 06 Apr 2024 22:44: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=3BI+7RtSN/G5+mDz2gxIBCN5mL1FvYweFXPfLO88q1g=; b=MzAbuj78HkdqFRtA9zLg/hjSvC jqPtJuzd/bQX3ahZcHonkanCCKHHBj+N4zddX6vZh5WFlouTrvkw6wkIsvEQXnG4Xvip4rY6HBeex a1RsC9h8ZVxhk6463PVnLUOoqocyFGaH6sz1rQZaSpKSypDF8Y2zxwRJ40CuSyTPstDxHUHWLhbTu pqQQbgZksKZjvsEjgTRjvuQAnHRyLEUyNNAio4aVXSvBgCkHJAUxKSpiaiSLqdupx5sNT2ORbMf6M 9oUMGmE/H4r3b1ZRCAlqP5goBVs0SD9McKwGngO2Lk2NNrGhXHdUxg2G9qbxKh87S1683sOsFQdV9 nT+ijVVw==; 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 1rtElZ-002dfY-5I for pgsql-announce@lists.postgresql.org; Sat, 06 Apr 2024 22:44: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 1rtElW-00ADFF-O7 for pgsql-announce@lists.postgresql.org; Sat, 06 Apr 2024 22:44:03 +0000 Content-Type: multipart/mixed; boundary="===============8506583837726461821==" MIME-Version: 1.0 Subject: pg_dumpbinary v2.16 released To: PostgreSQL Announce From: HexaCluster via PostgreSQL Announce Reply-To: gilles@hexacluster.ai Date: Sat, 06 Apr 2024 22:43:09 +0000 Message-ID: <171244338958.677.13634066800058666779@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 8e21a1085c26dc0297f619d2ac2df43d32e7b56f02a6bf0596edd37e5a6bf726 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============8506583837726461821== Content-Type: multipart/alternative; boundary="===============8788201669839420109==" MIME-Version: 1.0 --===============8788201669839420109== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable **Vientiane, Laos - April 6, 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 fixes data restoration for tables where schema or table names = contain the dollar sign (`$`). `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) --===============8788201669839420109== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable pg_dumpbinary v2.16 released
 

pg_dumpbinary v2.16 released

Vientiane, Laos - April 6, 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 fixes data restoration for tab= les where schema or table names contain the dollar sign ($).

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 HexaCluster. It was delivered on their beha= lf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to HexaCluster.

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/.
 
--===============8788201669839420109==-- --===============8506583837726461821==--