Re: [HACKERS] How to debug the wire protocol? - Mailing list pgsql-hackers

From Rui Pacheco
Subject Re: [HACKERS] How to debug the wire protocol?
Date
Msg-id 39B29636-F1B5-46AE-842F-C7D439B08A34@gmail.com
Whole thread Raw
In response to Re: [HACKERS] How to debug the wire protocol?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] How to debug the wire protocol?  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
I’ve been anxiously waiting for that reply but got nothing. I even mailed the mailing list manager again with no reply. And when I click on that link I get a server error: "An internal server error occurred.”

But thanks, this helps me focus on the problem.

On 9 Feb 2017, at 20:15, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Rui Pacheco <rui.pacheco@gmail.com> writes:
I’ve sent a similar email to the general mailing list but got no reply.

Uh, multiple people answered you, see
https://www.postgresql.org/message-id/flat/22DB2E08-6329-4EF8-B3E5-C0A7728A067B%40gmail.com

Is there a way to see how Postgres parses the message? I’ve set logging to DEBUG5 but the only thing I can see in the logs is, among other things, the message

ERROR:  invalid string in message
FATAL:  invalid frontend message type 63

That seems to comport with the theory I suggested before, that you were
sending an incorrect message length word --- although this additional
evidence indicates that the sent length is too short, not too long
which is what I'd been thinking.  Or possibly you left out required
field(s) of the message.  Anyway it's expecting a null-terminated string
and not finding one in the remaining message data.

regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] How to debug the wire protocol?
Next
From: David Steele
Date:
Subject: Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal