Hello,
thank you for your feedback.
I agree that modifying the COPY subprotocols is hard to do because it would
have an impact on the client ecosystem.
My understanding (which seems to be confirmed by what Tom Lane said) is
that the server discards the framing and
manages to make sense of the un
Hi,
On 2020-06-03 19:28:12 +0200, Jerome Wagner wrote:
> I have been working on a node.js streaming client for different COPY
> scenarios.
> usually, during CopyOut, clients tend to buffer network chunks until they
> have gathered a full copyData message and pass that to the user.
>
> In some cas
Hello,
I have been working on a node.js streaming client for different COPY
scenarios.
usually, during CopyOut, clients tend to buffer network chunks until they
have gathered a full copyData message and pass that to the user.
In some cases, this can lead to very large copyData messages. when ther
Jerome Wagner writes:
> now my question is the following :
> is it ok to consider that over the long term copyData is simply a transport
> container that exists only to allow the multiplexing of events in the
> protocol but that messages inside could be chunked over several copyData
> events ?
Ye
