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