Re: Protocol Question

Thanks Tom, you were in fact correct.

The client tripped over itself and forgot to finish reading some bytes when
reading a binary Text field. How that ended up looking like a NoData
message is beyond me but I have an extra check in place now that ensures
all types read all the bytes received for it. So another potential source
of errors fixed.

Thanks again,
/thomas

On Mon, Aug 18, 2014 at 7:55 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Thomas Heller <info(at)zilence(dot)net> writes:
> > I just encountered a weird protocol error while stress testing my client.
> > I'm receiving unexpected 'n'/NoData messages while reading 'D'/DataRow
> > messages.
>
> AFAICS, NoData can only be returned in response to Describe Statement
> or Describe Portal issued against a command that cannot return rows.
>
> If you can provide a counterexample for this claim, I'd be interested
> to see it. But my money is on confusion on the client side.
>
> regards, tom lane
>