From: | Thomas Heller <info(at)zilence(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Protocol Question |
Date: | 2014-08-18 09:12:14 |
Message-ID: | CAGTxmOsMraAf=aX0bSQtTLEHtTfzOC6uF1=wjqaU+TWB3qY-YQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Sabino Mullane | 2014-08-18 14:53:30 | DBD::Pg 3.4.0 released |
Previous Message | Tom Lane | 2014-08-18 05:55:35 | Re: Protocol Question |