Carlos Moreno <moreno@mochima.com> writes:
> Nothing relevant; there are about a dozen logged messages
> "Socket command type e unknown", and the line before is
> either another identical message, or a failed insert (a
> foreign key referential integrity violation).
You should look very hard at the part of your code that deals with
error reports from the server.
It might be worth logging the whole session between client and
server with tcpdump --- that'd be tedious to wade through, but
it might give some evidence of what's happening. It seems pretty
clear that the client is sending an incomplete message, but knowing
only one character of the broken message isn't much to help you
debug it. With a tcpdump trace you could see the whole packet ...
regards, tom lane