pg_dumpbinary v2.18 released

**Grenoble, France - June 22, 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.

This is a maintenance release that fixes two bugs in the restore process.

- Fix double copy statements when a table name requires to be quoted.
- Fix error when restoring a table with a GENERATED ALWAYS column.

`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)