Implement #204 - Add support for POSTGRES_BINARY copy method #205
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements #204
This PR adds support for the
POSTGRES_BINARY
copy format, that allows you to write files in the Postgres binary format. The files can be subsequently copied into Postgres using theirFORMAT binary
copy method. Example use case:DuckDB
Postgres
This uses the
PostgresBinaryWriter
that we have developed. Not all data types are supported - for now this is limited to types that directly map to Postgres -bool, smallint, int, bigint, float, double, decimal, date, time, timestamp, interval, uuid, blob, varchar
and composite types (arrays/structs). We could probably create a mapping for other types (e.g. unsigned types to Postgres' signed types).For now this only supports writing - although we could probably support reading from the binary format using the
PostgresBinaryReader
as well.