Thread: FATAL: invalid frontend message type 47 server closed the connection unexpectedly

I receive this message when I do a specific operation.
How can I debug something like this?

I use a Centos 4.0 distribution, postgresql version 8.1.3(I also used
diffrent distibutions and other versions of postgresql).
I connect to postgresql using perl DBD::Pg, using a tcp socket.

The error appears when I do a specific operation, but if I try many
times, it will work.
It works only if I try many times and fast.

Sterpu Victor <victor@ambra.ro> writes:
> I receive this message when I do a specific operation.
> How can I debug something like this?

It sounds like DBD::Pg is sending an invalidly formed message, or in
some other way violating the protocol.  Or maybe the backend got
confused.  Watching the session with a packet-sniffer would help to
nail down who's at fault.

            regards, tom lane

On Wed, Jan 17, 2007 at 05:34:27PM -0500, Tom Lane wrote:
> Sterpu Victor <victor@ambra.ro> writes:
> > I receive this message when I do a specific operation.
> > How can I debug something like this?
>
> It sounds like DBD::Pg is sending an invalidly formed message, or in
> some other way violating the protocol.  Or maybe the backend got
> confused.  Watching the session with a packet-sniffer would help to
> nail down who's at fault.

Well, DBD::Pg merely uses libpq. The most likely issue is somethong
that's not allowed, like using the same connection from multiple
threads. Or some other break in protocol.

We're going to need a lot more info to work this out. Incidently, 47 is
a capital G, IIRC.

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.