Greetings,
* Lőrinc Pap (lor...@gradle.com) wrote:
> Thanks for the quick response, Tom!
We prefer to not top-post on these lists, just fyi.
> What about implementing only the first part of my proposal, i.e. BINARY
> COPY without the redundant column count & size info?
For my part, at least, I
Thanks for the quick response, Tom!
What about implementing only the first part of my proposal, i.e. BINARY
COPY without the redundant column count & size info?
That would already be a big win - I agree the rest of the proposed changes
would only complicate the usage, but I'd argue that leaving
=?UTF-8?Q?L=C5=91rinc_Pap?= writes:
> We've switched recently from TEXT based COPY to the BINARY one.
> We've noticed a slight performance increase, mostly because we don't need
> to escape the content anymore.
> Unfortunately the binary protocol's output ended up being slightly bigger
> than the
Hey,
Our application sends millions of rows to the database every hour
using the COPY
IN protocol.
We've switched recently from TEXT based COPY to the BINARY one.
We've noticed a slight performance increase, mostly because we don't need
to escape the content anymore.
Unfortunately the binary
