| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: insufficient data left in message |
| Date: | 2008-02-21 15:39:41 |
| Message-ID: | 10576.1203608381@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dave Cramer <pg(at)fastcrypt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2008-02-21 15:42:58 | Re: Permanent settings |
| Previous Message | D'Arcy J.M. Cain | 2008-02-21 15:19:14 | Re: Permanent settings |