From: | HexaCluster via PostgreSQL Announce <announce-noreply(at)postgresql(dot)org> |
---|---|
To: | PostgreSQL Announce <pgsql-announce(at)lists(dot)postgresql(dot)org> |
Subject: | pg_dumpbinary v2.15 released |
Date: | 2024-02-21 17:12:19 |
Message-ID: | 170853553983.645.15527831702430169299@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-announce |
**Zurich, Switzerland - Febuary 14th, 2024**
## pg_dumpbinary
`pg_dumpbinary` dumps a PostgreSQL database to a binary format. The resulting dump must be restored
using `pg_restorebinary`, which is provided.
Version 2.15 has been published, this release adds a new option and fixes a bug reported by users since
last release.
- Add -w, --where command line option to pg_dumpbinary to apply a filter
to the data dumped. The filter will be used in a WHERE clause for data
export, this clause will be applied to all tables dumped.
- Fix error "DBD::Pg::db do failed: server closed the connection unexpectedly"
when the attempt to dump the pre-data section fail.
A full list of changes and acknowledgments can be found [here](https://github.com/lzlabs/pg_dumpbinary/releases/tag/v2.15)
`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 | 2024-02-21 19:40:57 | PostgreSQL JDBC 42.7.2, 42.6.1, 42.5.5, 42.4.4, 42.3.9, 42.2.28, and 42.2.28.jre7 Security update for CVE-2024-1597 |
Previous Message | pgmoneta via PostgreSQL Announce | 2024-02-16 08:43:22 | pgmoneta 0.9 |