Zurich, Switzerland - January 10th, 2024
pg_dumpbinary dumps a PostgreSQL database to a binary format. The resulting dump must be restored
pg_restorebinary, which is provided.
pg_dumpbinary 2.14 was released today, it adds two new options and fixes some bugs reported by users since last release.
-T options are used, to include or exclude child and partition tables. pg_dump will be used instead with options
--exclude-table-and-children. It requires PostgreSQL >= 16.
-V, --verbose option that lists tables included in the dump.
-A, --attach SNAPSHOT to be able to attach pg_dumpbinary to an existing snapshot instead of creating a dedicated one.
A full list of changes and acknowledgments can be found here
pg_dumpbinary is useful when:
pg_dump because the
total size of the escape/hex output exceeds 1Gb.
\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.
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
See the documentation for a more complete description of available features.
pg_dumpbinary is an Open Source project from LzLabs GmbH. Contributions and ideas are welcome. Send your ideas, features requests, or patches using GitHub's tools.