Re: insufficient data left in message - Mailing list pgsql-hackers

From Tom Lane
Subject Re: insufficient data left in message
Date
Msg-id 10576.1203608381@sss.pgh.pa.us
Whole thread Raw
In response to insufficient data left in message  (Dave Cramer <pg@fastcrypt.com>)
Responses Re: insufficient data left in message  (Dave Cramer <pg@fastcrypt.com>)
List pgsql-hackers
Dave Cramer <pg@fastcrypt.com> writes:
> This is a postgresql 8.2.5 backend. connected to a jdbc client.
> 2008-02-21 06:12:30 EST [18880] 10.21.0.21 ERROR:  insufficient data  
> left in message

AFAIK this means that the frontend sent an invalidly-formatted message.
There's some chance that the message was OK and the backend's message
parsing code is at fault, but I'd suspect the former first.

> So the question is: how to go about debugging this ?

Put a sniffer on the TCP session, or change the ERROR to a PANIC
and dig around in the core dump to see what the message was?

Also it might be worth updating to the latest JDBC driver, if you're
not on it already, just in case this is an already-fixed bug.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "D'Arcy J.M. Cain"
Date:
Subject: Re: Permanent settings
Next
From: "Greg Sabino Mullane"
Date:
Subject: Re: Permanent settings