From: | Gilles Darold via PostgreSQL Announce <announce-noreply(at)postgresql(dot)org> |
---|---|
To: | PostgreSQL Announce <pgsql-announce(at)lists(dot)postgresql(dot)org> |
Subject: | pg_dumpbinary v2.20 released |
Date: | 2025-06-11 00:48:10 |
Message-ID: | 174960289070.785.14772007853079727860@wrigleys.postgresql.org |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-announce |
**Antananarivo, Madagascar - June 04, 2025**
## pg_dumpbinary
`pg_dumpbinary` dumps a PostgreSQL database to a binary format. The resulting dump must be restored
using `pg_restorebinary`, which is provided.
This is a maintenance release that fixes some issues reported by users since last
release and adds an new command line option to the `pg_restorebinary` command.
* Add `-V, --verbose` option to `pg_restorebinary`.
* Change directory to writable one when sudo -u is used to avoid
pg_restore to complain about "could not change directory" when
the current directory is not writable by the running user. In
this case `pg_dumpbinary` and `pg_restorebinary` will require an
absolute path respectively for output and input directory.
* Do not import the `tmpdir()` method when importing File::Spec.
* Fix returned error code when no input directory or missing parameters.
`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.lzlabs.com/). Contributions and ideas are
welcome. Send your ideas, features requests, or patches using GitHub's tools.
Links :
* Documentation: [https://github.com/lzlabs/pg_dumpbinary/blob/master/README.md](https://github.com/lzlabs/pg_dumpbinary/blob/master/README.md)
* Download: [https://github.com/lzlabs/pg_dumpbinary/releases/](https://github.com/lzlabs/pg_dumpbinary/releases/)
* Support: use GitHub report tool at [https://github.com/lzlabs/pg_dumpbinary/pg_dumpbinary/issues](https://github.com/lzlabs/pg_dumpbinary/pg_dumpbinary/issues)
From | Date | Subject | |
---|---|---|---|
Next Message | JDBC Project via PostgreSQL Announce | 2025-06-13 12:51:08 | PostgreSQL JDBC 42.7.7 Security update for CVE-2025-49146 |
Previous Message | PoWA via PostgreSQL Announce | 2025-06-11 00:47:58 | powa-archivist 5.0.3 is out! |